# CVE-2013-3660: Microsoft Win32k Privilege Escalation

> Local attackers can gain privileges by exploiting a pointer initialization flaw in the Windows kernel-mode driver win32k.sys.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 28 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 May 2013
- **Updated:** 22 Oct 2025
- **Also known as:** CVE-2013-3130, GHSA-f2wh-c6mm-3vrx

## What is CVE-2013-3660?

CVE-2013-3660 is a high-severity vulnerability in Microsoft Windows 7, published on 24 May 2013. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### 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."

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2013-3660?

It affects 8 products.


Products: Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows Rt, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista, Microsoft Windows Xp.

## How do I fix CVE-2013-3660?

No fix has been published for CVE-2013-3660 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 18 Apr 2022.

## Is CVE-2013-3660 being exploited?

Yes. Attackers have exploited CVE-2013-3660 in the wild since at least 28 Mar 2022.

Public exploit code:

- CVE-2013-3660的x64 win7平台EXP源代码，成功率100%。 (github_poc): https://github.com/ExploitCN/CVE-2013-3660-x64-WIN7
- Windows EPATHOBJ::pprFlattenRec Local Privilege Escalation (metasploit)
- Microsoft Windows - Win32k!EPATHOBJ::pprFlattenRec Uninitialized Next Pointer Testcase (exploitdb)
- Microsoft Windows NT/2000/2003/2008/XP/Vista/7/8 - 'EPATHOBJ' Local Ring (exploitdb)
- Microsoft Windows - 'EPATHOBJ::pprFlattenRec' Local Privilege Escalation (Metasploit) (exploitdb)
- https://github.com/kikozz/CVE-2013-3660-win32k.sys (github_poc): https://github.com/kikozz/CVE-2013-3660-win32k.sys

## 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-2013-3660 and fix it if it is affected.

What it is: CVE-2013-3660 is a high-severity vulnerability in Microsoft Windows 7, published on 24 May 2013. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2013-3660 in the wild since at least 28 Mar 2022.

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-2013-3660/ (Markdown: https://insights.sbomify.com/CVE-2013-3660/index.md)
```

## Sources

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

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