win32k.sys in the kernel-mode drivers in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2…
No fixed version listed yet.Check the vendor advisory. References ↓
The flaw is in win32k.sys, the kernel-mode driver component of Microsoft Windows, which does not properly handle objects in memory across several Windows XP, Vista, Server 2003/2008/2012, 7, 8 and RT releases. A local user running a crafted application can exploit it to gain elevated privileges, so the attacker needs local code execution on the affected system but no network access.
Official description · CVE.org
win32k.sys in the kernel-mode drivers in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows Server 2012, and Windows RT does not properly handle objects in memory, which allows local users to gain privileges via a crafted application, aka "Win32k Memory Allocation Vulnerability."
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 9 years after disclosure. Public exploit code (PoC-in-GitHub) appeared 2 months after disclosure.
- Disclosedday 0
- Public exploit codePoC-in-GitHub+2 mo
- First seen exploitedVulnCheck KEV evidence+9 yrs
What security researchers reported
Not named in any threat report yetAlso mentioned in 3 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.