Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2017-0005: Windows GDI Elevation of Privilege Vulnerability

Published Mar 17, 2017 · Updated 16 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS11.0%96th percentile
CISA KEVYesAdded May 24, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2017-0005CWE-269

CVE-2017-0005 is a local elevation-of-privilege vulnerability in the Microsoft Windows Graphics Device Interface (GDI). A local user can exploit it by executing a specially crafted application. Affected platforms include Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1 and RT 8.1; Windows Server 2012 and 2012 R2; and Windows 10 initial release, version 1511, and version 1607. The vulnerability is exploited by EpMe and the related Jian exploit and has been used by APT31, also known as ZIRCONIUM. It is distinct from CVE-2017-0001, CVE-2017-0025, and CVE-2017-0047.

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 allows a local attacker to elevate privileges on an affected Windows system. Observed use of the EpMe exploit within the DanderSpritz framework enabled loading a malicious kernel driver, supporting subsequent kernel-level operations and stealth. The vulnerability therefore enables an attacker with an existing local execution foothold to obtain substantially greater control over the host.

Mitigation

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

Until patches are fully deployed, reduce opportunities for local code execution by enforcing application control, least-privilege user rights, and strong restrictions on execution of untrusted binaries and scripts. Limit interactive access to systems, monitor for anomalous privilege-escalation behavior and exploit artifacts associated with EpMe, and use endpoint protection capable of detecting exploitation attempts and suspicious post-exploitation activity. These measures do not remove the vulnerability but can reduce exploitability and impact.

Remediation

Patch, then assume compromise.

Apply the Microsoft security update that addresses CVE-2017-0005 on all affected Windows versions. Priority should be given to systems where untrusted code can be executed locally, including workstations and terminal or multi-user environments. Standard patch-validation and rollout procedures should be followed, and unsupported operating systems should be upgraded or retired where possible.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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 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
Microsoft CorporationWindows Vistaoperating_system
FAQ

Frequently asked questions

Is CVE-2017-0005 exploited in the wild?
Yes. As of Nov 4, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on May 24, 2022.
Is there a public exploit for CVE-2017-0005?
Yes. As of Nov 4, 2026, Mallory has reports of a public exploit for CVE-2017-0005.
Is there a patch for CVE-2017-0005?
Apply the Microsoft security update that addresses CVE-2017-0005 on all affected Windows versions. Priority should be given to systems where untrusted code can be executed locally, including workstations and terminal or multi-user environments.
What products are affected by CVE-2017-0005?
Microsoft Corporation Windows 7, Microsoft Corporation Windows 8.1, Microsoft Corporation Windows Server 2008, Microsoft Corporation Windows Server 2012, Microsoft Corporation Windows Vista, and 5 more.
How severe is CVE-2017-0005?
CVE-2017-0005 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 11.0% (96th percentile) as of Nov 4, 2026.
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 evidence8Every report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, 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.