basicsecurity.net
Proof, not just disclosure.
Threats / Microsoft / CVE-2017-0005
CVE-2017-0005 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Microsoft Windows vulnerability

A buffer overflow in Microsoft Windows Graphics Device Interface (GDI) allows local users to escalate privileges through a crafted application.

Verdict

Today item — known-exploited.

This privilege escalation vulnerability in GDI has been exploited in the wild. Local attackers can leverage buffer overflow conditions to gain elevated system privileges, though no ransomware campaigns have been directly attributed to this flaw.

CISA KEV Yes · 2022-05-243EPSS 0.11022 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
8 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-05-24).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.11022 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious application that triggers a buffer overflow in the GDI subsystem.
Business
An attacker gains local code execution with elevated privileges on affected Windows systems.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute my application on a target system where I already have user-level access.
Business
The organization loses control of system integrity as the attacker obtains administrative privileges.
3

Lateral reach — past segmentation narrative 3

Attacker
I use the elevated privileges to install persistent backdoors or access sensitive data.
Business
Critical business systems and confidential information become compromised and potentially exfiltrated.
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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Public PoC available (VulnCheck)
  • 8 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by microsoft (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by microsoftCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.