# CVE-2011-1652: Misconfiguration in n/a

> Remote attackers can intercept IPv4 traffic via man-in-the-middle attacks by exploiting Windows 7's default IPv6 preference and lack of Router Advertisement validation.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8xjw-mv36-c7hq

## What is CVE-2011-1652?

CVE-2011-1652 is a medium-severity vulnerability in Microsoft Windows 7, published on 6 Apr 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-16

## Which versions are affected by CVE-2011-1652?

It affects 1 product.


Products: Microsoft Windows 7.

## How do I fix CVE-2011-1652?

No fix has been published for CVE-2011-1652 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-1652 being exploited?

There is no known exploitation of CVE-2011-1652 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Windows 7

- [CVE-2015-1635](https://insights.sbomify.com/CVE-2015-1635/): Microsoft HTTP.sys Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-2360](https://insights.sbomify.com/CVE-2015-2360/): Microsoft Win32k Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6324](https://insights.sbomify.com/CVE-2014-6324/): Microsoft Kerberos Key Distribution Center (KDC) Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6332](https://insights.sbomify.com/CVE-2014-6332/): Microsoft Windows Object Linking & Embedding (OLE) Automation Array Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2014-4148](https://insights.sbomify.com/CVE-2014-4148/): Microsoft Windows Remote Code Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1652 and fix it if it is affected.

What it is: CVE-2011-1652 is a medium-severity vulnerability in Microsoft Windows 7, published on 6 Apr 2011. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-1652 in the wild and no public exploit code.

Affected product: Microsoft Windows 7. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-1652/ (Markdown: https://insights.sbomify.com/CVE-2011-1652/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-1652
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-1652
- OSV: https://osv.dev/vulnerability/CVE-2011-1652

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-1652/
Summaries are generated and may contain mistakes; the official description above is the record.