• Platformchevron right
  • Solutionschevron right
  • Modern NDRchevron right
  • Resourceschevron right
  • Companychevron right

DETECTION OVERVIEW

LLMNR Poisoning

Risk Factors

LLMNR is an older and vulnerable protocol that is typically disabled, so the likelihood of an attack is low. However, if an attacker impersonates a proxy or harvests user credentials, they can ultimately gain privileged information or unauthorized access to assets on your network.

The system might change the risk score for this detection.

Kill Chain

Exploitation

Risk Score

Detection diagram
Next in Exploitation: Log4Shell JNDI Injection Attempt

Attack Background

When a DNS request for a hostname cannot be resolved or no DNS server is available (1), some clients will broadcast a query to all local devices over LLMNR (2). If an attacker is listening, they can respond and impersonate the requested host (3). If the host is an authenticated resource, that client might send user credentials to the attacker.

Mitigation Options

Quarantine the attacking and victim devices if they are compromised

If LLMNR is not required for your Windows environment, disable LLMNR in local security settings or by group policy

Ensure secure password policies are applied to your network devices to offset potential damage in the aftermath of an attack

MITRE ATT&CK ID

What else can RevealX do for you?