# CVE-2015-1701: Microsoft Win32k Privilege Escalation

> Local attackers can gain elevated privileges via a crafted application exploiting the Win32k.sys kernel driver in Windows.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Mar 2022 (CISA KEV), used in ransomware
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2015
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-rq9p-fw9r-ppg4

## What is CVE-2015-1701?

CVE-2015-1701 is a high-severity vulnerability in Microsoft Windows 2003 Server, published on 21 Apr 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Win32k.sys in the kernel-mode drivers in Microsoft Windows Server 2003 SP2, Vista SP2, and Server 2008 SP2 allows local users to gain privileges via a crafted application, as exploited in the wild in April 2015, aka "Win32k Elevation of Privilege Vulnerability."

## Which versions are affected by CVE-2015-1701?

It affects 4 products.


Products: Microsoft Windows 2003 Server, Microsoft Windows 7, Microsoft Windows Server 2008, Microsoft Windows Vista.

## How do I fix CVE-2015-1701?

No fix has been published for CVE-2015-1701 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 24 Mar 2022.

## Is CVE-2015-1701 being exploited?

Yes. Attackers have exploited CVE-2015-1701 in the wild since at least 3 Mar 2022, including in ransomware campaigns.

Public exploit code:

- Win32k LPE vulnerability used in APT attack (github_poc): https://github.com/hfiref0x/CVE-2015-1701
- Windows ClientCopyImage Win32k Exploit (metasploit)
- Microsoft Windows - Local Privilege Escalation (MS15-051) (exploitdb)
- Microsoft Windows - ClientCopyImage Win32k (MS15-051) (Metasploit) (exploitdb)
- Unspecified vulnerability in Microsoft Windows before 8 allows local users to gain privileges via unknown vectors, as exploited in the wild in April 2015   (Base Score: 7.2 HIGH)   Current Description Win32k.sys in the kernel-mode drivers in Microsoft Windows Server 2003 SP2, Vista SP2, and Server 2008 SP2 allows local users to gain privileges via a crafted application, as exploited in the wild in April 2015, aka "Win32k Elevation of Privilege Vulnerability  (github_poc): https://github.com/Anonymous-Family/CVE-2015-1701
- https://github.com/Anonymous-Family/CVE-2015-1701-download (github_poc): https://github.com/Anonymous-Family/CVE-2015-1701-download

## Other vulnerabilities in Microsoft Windows 2003 Server

- [CVE-2008-0015](https://insights.sbomify.com/CVE-2008-0015/): Microsoft Windows Video ActiveX Control Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2013-5065](https://insights.sbomify.com/CVE-2013-5065/): Microsoft Windows Kernel Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2011-1268](https://insights.sbomify.com/CVE-2011-1268/): Code injection in n/a (critical 10.0)
- [CVE-2011-1868](https://insights.sbomify.com/CVE-2011-1868/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-0661](https://insights.sbomify.com/CVE-2011-0661/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1701 and fix it if it is affected.

What it is: CVE-2015-1701 is a high-severity vulnerability in Microsoft Windows 2003 Server, published on 21 Apr 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2015-1701 in the wild since at least 3 Mar 2022, including in ransomware campaigns.

Affected product: Microsoft Windows 2003 Server. 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-2015-1701/ (Markdown: https://insights.sbomify.com/CVE-2015-1701/index.md)
```

## Sources

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

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