# CVE-2015-0010: Security feature bypass in n/a

> Local attackers can bypass CNG decryption restrictions to read encrypted data by exploiting impersonation token flaws in the kernel driver.

- **Severity:** Low 1.9 (`AV:L/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** CVE-2015-2010, GHSA-m8v6-5m42-3wc3

## What is CVE-2015-0010?

CVE-2015-0010 is a low-severity vulnerability in Microsoft Windows 7, published on 11 Feb 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The CryptProtectMemory function in cng.sys (aka the Cryptography Next Generation driver) in the kernel-mode drivers in Microsoft Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1, when the CRYPTPROTECTMEMORY_SAME_LOGON option is used, does not check an impersonation token's level, which allows local users to bypass intended decryption restrictions by leveraging a service that (1) has a named-pipe planting vulnerability or (2) uses world-readable shared memory for encrypted data, aka "CNG Security Feature Bypass Vulnerability" or MSRC ID 20707.

Weakness: CWE-310

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

It affects 9 products.


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

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

No fix has been published for CVE-2015-0010 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-0010 being exploited?

There is no known exploitation of CVE-2015-0010 in the wild and no public exploit code.

Public exploit code:

- Microsoft Windows - Local Privilege Escalation (MS15-010) (exploitdb)

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

What it is: CVE-2015-0010 is a low-severity vulnerability in Microsoft Windows 7, published on 11 Feb 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-0010 in the wild and no public exploit code.

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

## Sources

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

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