Threats / Microsoft / CVE-2017-0005

CVE-2017-0005 · EUVD no mirror located · GCVE no mirror located Verified 2026-09-19

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-24⁴EPSS 0.11022 (verify live)⁵Exploit Public PoC⁶CVSS 7.8 (CISA)³CISA SSVC Exploitation: active · Automatable: no · Impact: total³

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.

vulncheck.com ↗Confirmed

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.

api.msrc.microsoft.com ↗docs.google.com ↗microsoft.com ↗secureworks.com ↗Confirmed

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.

FIRST EPSS ↗High

Severity / affected

CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) · Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.

CISA-ADP ↗Reported

Weakness (CWE)

Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.

NVD ↗Reported

CISA SSVC (triage disposition)

Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.

CISA-ADP ↗Reported

Currency of the record

CISA added this to its KEV catalog 1894 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.

CISA KEV ↗CVE.org ↗Reported

WeaknessCWE-119 · Memory Buffer Bounds ErrorMemory safety

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.

Why it matters

— the attack path, told twice: adversary, then board

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.

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.

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.

What to do

— defensible action

Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.¹

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.

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)

CVSS 7.8 — CISA-assigned (CVE.org ADP)

CISA SSVC triage disposition (CVE.org ADP)

CWE weakness mapping (NVD feed — CNA left none)

Public exploit availability

Catalogued by microsoft (CNA)

Named finder/reporter credit (CVE.org)

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.

Disclosure & credit²

Catalogued by microsoftCNA

Credited with finding itLockheed Martin Computer Incident Response Teamfinder

Found an error? Propose a correction.

A correction is a cited counter-claim — it must cite a source, gets reviewed by a second human, and is never auto-applied. See the correction convention and our identity npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.

With JavaScript off: publish a signed kind 1111 Nostr event tagging ["r", "https://basicsecurity.net/threat/cve-2017-0005.html"], ["v", "sha256:8958e0d4cd61d9cf74a409e5549f3316cb4f6dc55067d6f5de010b5a21b56a77"] (the record version), plus ["src", "<your source URL>"] and ["t", "correction"], per the correction convention. Our identity: npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y. Cite-or-die: an event with no src is a coverage finding, not a proposal.