Skip to content
StrikeOps

IPv6 DNS Takeover (DHCPv6 Spoofing)

HighTypical severity Network and infrastructureATT&CK T1557

01Description

Windows hosts on the internal network had IPv6 enabled but no legitimate DHCPv6 server was present. Windows prefers IPv6 and requests configuration via DHCPv6, so an attacker on the network can answer these requests and set themselves as the DNS server for affected hosts.

02Impact

As the DNS server, an attacker can direct hosts to authenticate to attacker-controlled services and relay that authentication to LDAP or Active Directory Certificate Services. This can be used to create machine accounts, configure delegation or obtain certificates, leading to privilege escalation in the domain.

03Severity

Typically

High

Typically High. Usually High because it requires no credentials and can lead to relayed authentication against LDAP or AD CS. Medium if IPv6 is disabled on most hosts or LDAP signing and channel binding are enforced.

04How to verify

  1. 1Observe DHCPv6 solicit traffic from Windows hosts on the segment.
  2. 2Where authorized, use a tool such as mitm6 in a limited, time-boxed window against named test hosts to confirm hosts accept the rogue DNS server.
  3. 3Check whether LDAP signing and channel binding are enforced on domain controllers.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1If IPv6 is not used internally, block DHCPv6 and router advertisement traffic via Windows Firewall rules applied by Group Policy, rather than disabling the IPv6 stack.
  2. 2If IPv6 is used, deploy DHCPv6 guard and RA guard on network switches.
  3. 3Enforce LDAP signing and LDAP channel binding on domain controllers.
  4. 4Disable the Web Proxy Auto-Discovery (WPAD) service if not required.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo