CVE-2011-0670 json
Use-after-free vulnerability in win32k.sys in the kernel-mode drivers in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows…
published 2011-04-13 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-0688
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
Use-after-free vulnerability in win32k.sys in the kernel-mode drivers in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2, R2, and R2 SP1, and Windows 7 Gold and SP1 allows local users to gain privileges via a crafted application that leverages incorrect driver object management, a different vulnerability than other "Vulnerability Type 1" CVEs listed in MS11-034, aka "Win32k Use After Free Vulnerability."
Exploit prediction
1.43% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-399 Resource Management Errors
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2011/ms11-034
vendor-advisory
-
us-cert.gov
/cas/techalerts/TA11-102A.html
third-party-advisory, us-government-resource
-
securityfocus.com
/bid/47205
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/66399
vdb-entry
-
osvdb.org
/71744
vdb-entry
-
vupen.com
/english/advisories/2011/0952
vdb-entry
- support.avaya.com /css/P8/documents/100133352
-
secunia.com
/advisories/44156
third-party-advisory
- blogs.technet.com /b/srd/archive/2011/04/12/ms11-034-addressing-vulnerabilities-in-the-win32k-subsystem.aspx
-
securitytracker.com
/id?1025345
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A12337
vdb-entry, signature
Sources
- CVE List CVE-2011-0670
- NVD CVE-2011-0670
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.