# CVE-2017-0213: Microsoft Windows Privilege Escalation

> An attacker can gain elevated privileges by running a specially crafted application exploiting the Windows COM Aggregate Marshaler.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 28 Mar 2022 (CISA KEV), used in ransomware
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 May 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-6pc8-xvmj-x3wh

## What is CVE-2017-0213?

CVE-2017-0213 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 12 May 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

Windows COM Aggregate Marshaler in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allows an elevation privilege vulnerability when an attacker runs a specially crafted application, aka "Windows COM Elevation of Privilege Vulnerability". This CVE ID is unique from CVE-2017-0214.

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

It affects 10 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1511, Microsoft Windows 10 1607, Microsoft Windows 10 1703, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016.

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

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

## Is CVE-2017-0213 being exploited?

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

Public exploit code:

- CVE-2017-0213 for command line (github_poc): https://github.com/zcgonvh/CVE-2017-0213
- Fixed No Virus Manual Automatic Loader exe no zip because zip picks up the anti virus detector. (github_poc): https://github.com/eonrickity/CVE-2017-0213
- A version of CVE-2017-0213 that I plan to use with an Empire stager (github_poc): https://github.com/jbooz1/CVE-2017-0213
- Microsoft Windows - COM Aggregate Marshaler/IRemUnknown2 Type Confusion Privilege Escalation (exploitdb)
- https://github.com/shaheemirza/CVE-2017-0213- (github_poc): https://github.com/shaheemirza/CVE-2017-0213-
- https://github.com/billa3283/CVE-2017-0213 (github_poc): https://github.com/billa3283/CVE-2017-0213

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-0213 and fix it if it is affected.

What it is: CVE-2017-0213 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 12 May 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-0213 in the wild since at least 28 Mar 2022, including in ransomware campaigns.

Affected product: Microsoft Windows 10 1507. 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-0213/ (Markdown: https://insights.sbomify.com/CVE-2017-0213/index.md)
```

## Sources

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

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