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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 3 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Windows privilege escalation vulnerability reportedly used by Kingminer during infection to gain elevated privileges and hinder defensive intervention.
A Windows local privilege escalation vulnerability frequently used by Makop operators to obtain SYSTEM-level privileges.
A Windows privilege escalation vulnerability mentioned in a gaming-sector incident with unresolved attribution and only possible overlap with APT27.
A vulnerability associated through VirusTotal tags with variants of the MyComEop privilege escalation tool and backdoor. Campaign loaders decrypted related payloads, but the report does not conclusively establish that the recovered payloads exploited this specific CVE.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.