Threats / Microsoft / CVE-2017-0001
CVE-2017-0001
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Microsoft Graphics Device Interface (GDI) vulnerability
A privilege escalation vulnerability in Microsoft's Graphics Device Interface (GDI) allows local users to gain elevated privileges on affected Windows systems.
Verdict
Today item — known-exploited.
Local privilege escalation in GDI affecting Windows Vista through Windows 10. Exploited in the wild. No CVSS score available. EPSS score 0.48 indicates moderate exploitation probability.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
2 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-03).
Probability (EPSS)
EPSS 0.03114 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Graphics Device Interface (GDI). Confirm exact fixed builds in the vendor advisory.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I execute a malicious GDI operation from my local user account to trigger the vulnerability.
Business
An unprivileged user gains system-level access, enabling full system compromise and lateral movement.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I use the elevated privileges to install persistent malware or backdoors on the compromised system.
Business
Attackers establish durable footholds for data exfiltration, espionage, or further network infiltration.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05