CVE-2013-3660: Microsoft Win32k Privilege Escalation
Microsoft Win32k · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-28.
- CVSS v3.1 (CISA ADP)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 39%
- higher than 98.6% of all CVEs
- Added to CISA KEV
- 2022-03-28
- US federal due date 2022-04-18
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2013-3660 explained
CVE-2013-3660 is a privilege escalation vulnerability in the Win32k kernel-mode driver (win32k.sys) of Microsoft Windows. A pointer in the EPATHOBJ::pprFlattenRec function is not properly initialized, which lets local users gain elevated privileges. CISA lists it as known to be exploited by attackers.
Impact
A local user can gain write access to the PATHRECORD chain in kernel memory and use it to gain higher privileges. The attack needs local access and some user interaction, but no prior privileges. CISA rates the technical impact as total, with high impact on confidentiality, integrity and availability. It is not automatable at scale, but attackers are known to exploit it.
Who is affected
The description names win32k.sys 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, and Windows Server 2012. The CVE record itself lists no affected versions for Microsoft Win32k. It names no fixed version. Check the vendor advisory for the applicable updates.
Written with AI from the data on this page and checked against it automatically.
Official description
The EPATHOBJ::pprFlattenRec function in 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, and Windows Server 2012 does not properly initialize a pointer for the next object in a certain list, which allows local users to obtain write access to the PATHRECORD chain, and consequently gain privileges, by triggering excessive consumption of paged memory and then making many FlattenPath function calls, aka "Win32k Read AV Vulnerability."
CISA required action: Apply updates per vendor instructions.
CISA notes
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: docs.microsoft.com/en-us/security-updates/securitybulleti…
- CISA's deadline for US federal agencies: 2022-04-18 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security updates for this vulnerability on all affected Windows systems, as CISA's required action states.
- Inventory systems running the Windows versions named in the description and confirm the update is installed.
- Limit local and interactive logon rights to trusted users to reduce the chance of local privilege escalation.
- Check systems for signs of compromise, such as unexpected privileged accounts or processes.
- Replace Windows versions that no longer receive updates from Microsoft with supported versions.
The CVE record names no fixed version. Follow the Microsoft vendor advisory to identify and install the correct updates for each Windows version, as CISA requires ("Apply updates per vendor instructions."). Until updates are confirmed, restrict local logon to trusted users and monitor systems for unexpected privilege changes.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Questions about CVE-2013-3660
- Can this vulnerability be exploited remotely?
- No. The attack vector is local. An attacker needs to run code on the system, and user interaction is required. The result is elevated privileges with total control of the affected component.
- Is CVE-2013-3660 exploited in the wild?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-28, with a US federal due date of 2022-04-18. Whether it is used in ransomware campaigns is unknown.
- Which fixed version should I install?
- The CVE record names no fixed version. Use the Microsoft vendor advisory to find the update for each affected Windows version.
Written with AI from the data on this page and checked against it automatically.
References
Vendor
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.