CVE-2011-1652 json
The default configuration of Microsoft Windows 7 immediately prefers a new IPv6 and DHCPv6 service over a currently used IPv4 and DHCPv4 se…
published 2011-04-06 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1652
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 12.3%
- EPSS 12.3% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
The default configuration of Microsoft Windows 7 immediately prefers a new IPv6 and DHCPv6 service over a currently used IPv4 and DHCPv4 service upon receipt of an IPv6 Router Advertisement (RA), and does not provide an option to ignore an unexpected RA, which allows remote attackers to conduct man-in-the-middle attacks on communication with external IPv4 servers via vectors involving RAs, a DHCPv6 server, and NAT-PT on the local network, aka a "SLAAC Attack." NOTE: it can be argued that preferring IPv6 complies with RFC 3484, and that attempting to determine the legitimacy of an RA is currently outside the scope of recommended behavior of host operating systems
Exploit prediction
12.33% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- resources.infosecinstitute.com http://resources.infosecinstitute.com/slaac-attack/ referenced PoC, tagged "exploit" by a source, unverified
- lists.immunityinc.com https://lists.immunityinc.com/pipermail/dailydave/20110404/000122.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-16 Configuration
References
-
resources.infosecinstitute.com
/slaac-attack/
exploit
-
lists.immunityinc.com
/pipermail/dailydave/20110404/000122.html
mailing-list, exploit
Sources
- CVE List CVE-2011-1652
- NVD CVE-2011-1652
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.