CVE-2017-0005: Windows GDI Elevation of Privilege Vulnerability
- Vendor
- Microsoft Corporation
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.
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.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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.
References
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.
Recent activity
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.