# CVE-2017-0101: Microsoft Windows Transaction Manager Privilege Escalation

> Local attackers can gain elevated privileges on Microsoft Windows systems by exploiting a vulnerability in the Transaction Manager kernel-mode drivers.

- **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 15 Mar 2022 (CISA KEV), used in ransomware
- **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:** 17 Mar 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-5cr3-r8pg-5j63

## What is CVE-2017-0101?

CVE-2017-0101 is a high-severity vulnerability in Microsoft Windows 7, published on 17 Mar 2017. 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 kernel-mode drivers in Transaction Manager in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2; Windows 7 SP1; Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1; Windows 10 Gold, 1511, and 1607; and Windows Server 2016 allow local users to gain privileges via a crafted application, aka "Windows Elevation of Privilege Vulnerability."

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

## Which versions are affected by CVE-2017-0101?

It affects 3 products.


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

## How do I fix CVE-2017-0101?

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

## Is CVE-2017-0101 being exploited?

Yes. Attackers have exploited CVE-2017-0101 in the wild since at least 15 Mar 2022, including in ransomware campaigns.

Public exploit code:

- Microsoft Windows Kernel (7 x86) - Local Privilege Escalation (MS17-017) (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-2017-0101 and fix it if it is affected.

What it is: CVE-2017-0101 is a high-severity vulnerability in Microsoft Windows 7, published on 17 Mar 2017. 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-2017-0101 in the wild since at least 15 Mar 2022, including in ransomware campaigns.

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

## Sources

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

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