Vulnerability record · CVE-2010-1892 · published 11 August 2010
CVE-2010-1892: Windows TCP/IP stack IPv6 malformed packet memory corruption DoS
Microsoft · Windows 7
The TCP/IP stack in Windows Vista SP1/SP2, Windows Server 2008 Gold/SP2/R2, and Windows 7 mishandles malformed IPv6 packets, leading to memory corruption. A remote attacker can send multiple crafted packets to hang the system, causing a denial of service. The flaw is remotely reachable without authentication, making it a serious availability risk for exposed hosts.
Description
The TCP/IP stack in Microsoft Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7 does not properly handle malformed IPv6 packets, which allows remote attackers to cause a denial of service (system hang) via multiple crafted packets, aka "IPv6 Memory Corruption Vulnerability."
AV:N/AC:L/Au:N/C:N/I:N/A:C
Automated analysis
high priorityRemote, unauthenticated denial of service with complete availability impact and high EPSS, though no KEV listing or confirmed in-the-wild exploitation is recorded.
What it is
The TCP/IP stack in Windows Vista SP1/SP2, Windows Server 2008 Gold/SP2/R2, and Windows 7 mishandles malformed IPv6 packets, leading to memory corruption. A remote attacker can send multiple crafted packets to hang the system, causing a denial of service. The flaw is remotely reachable without authentication, making it a serious availability risk for exposed hosts.
Impact
An attacker can cause a full system hang (denial of service) on affected Windows hosts. No confidentiality or integrity impact is described; the effect is loss of availability.
Attack surface
Reached over the network via IPv6 traffic to the target's TCP/IP stack; the CVSS vector AV:N/AC:L/Au:N indicates no authentication and no user interaction are required. Exploitation depends on the host processing IPv6 packets, so systems with IPv6 disabled or filtered may not be reachable.
Exploitation
Not listed in CISA KEV and no public exploit references are tagged in the record, but EPSS is high (0.61997, 99.1st percentile), suggesting elevated likelihood of attempted exploitation. The references are vendor and government advisories only.
What to do
- Apply Microsoft security bulletin MS10-058 (the vendor fix for this issue) as the first action.
- Disable IPv6 on hosts that do not require it, or block inbound IPv6 at the perimeter where feasible.
- Filter or rate-limit malformed IPv6 traffic at network boundaries and on host firewalls.
- Monitor affected legacy Windows versions and plan migration off Vista, Server 2008, and Windows 7 where possible.
Detection
- Monitor for repeated malformed or anomalous IPv6 packets targeting affected hosts.
- Alert on unexpected system hangs or reboots on Windows Vista, Server 2008, and Windows 7 systems.
- Review IPv6 traffic logs for unusual packet patterns or floods from external sources.
- Correlate host availability drops with inbound IPv6 traffic spikes.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
3 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
Track CVE-2010-1892 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2010-1892), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.