Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2017-0213: Windows COM Aggregate Marshaler Local Privilege Escalation

Published May 12, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.3High · v3.1
EPSS84.3%100th percentile
CISA KEVYesAdded Mar 28, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2017-0213CWE-269

CVE-2017-0213 is a local privilege-escalation vulnerability in the Windows COM Aggregate Marshaler. An attacker who runs a specially crafted application can execute arbitrary code with elevated privileges. Affected platforms include Windows Server 2008 SP2 and 2008 R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 and 2012 R2, Windows RT 8.1, Windows 10 initial release and versions 1511, 1607, and 1703, and Windows Server 2016. Microsoft fixed the vulnerability in May 2017. It is distinct from CVE-2017-0214.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation elevates an attacker's privileges on the affected Windows system and permits arbitrary code execution with elevated rights, including running tools as administrator. The vulnerability has been exploited in post-compromise operations by espionage and ransomware actors, including APT33, Ragnar Locker, and Nefilim.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by limiting local code execution opportunities, enforcing least privilege, restricting interactive logon rights, and preventing untrusted users from executing arbitrary applications. Application control, endpoint detection and response, and hardening measures that block or detect suspicious child processes and privilege-escalation behavior can reduce exploitation opportunities. Monitoring for abnormal privilege transitions and post-exploitation tooling can help detect attempted abuse.

Remediation

Patch, then assume compromise.

Apply the Microsoft security update addressing CVE-2017-0213, released in May 2017, or a superseding update applicable to the affected Windows version.

Public exploits

Exploits

No validated public exploits yet. Hidden: 2 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1511operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1703operating_system
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Rt 8.1operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2016operating_system
FAQ

Frequently asked questions

Is CVE-2017-0213 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 28, 2022.
Is there a public exploit for CVE-2017-0213?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2017-0213.
Is there a patch for CVE-2017-0213?
Apply the Microsoft security update addressing CVE-2017-0213, released in May 2017, or a superseding update applicable to the affected Windows version.
What products are affected by CVE-2017-0213?
Microsoft Corporation Windows 7, Microsoft Corporation Windows 8.1, Microsoft Corporation Windows Rt 8.1, Microsoft Corporation Windows Server 2008, Microsoft Corporation Windows Server 2012, and 5 more.
How severe is CVE-2017-0213?
CVE-2017-0213 has a CVSS v3.1 score of 7.3 (High) and an EPSS score of 84.3% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+13 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence7Every report linking this CVE to a named adversary.
Associated malware10Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.