LiveActive security incident?Get immediate response
CVE Record

CVE-2017-0005: The Graphics Device Interface (GDI) in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Win...

The Graphics Device Interface (GDI) in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; and Windows 10 Gold, 1511, and 1607 allows local users to gain privileges via a crafted application, aka "Windows GDI Elevation of Privilege Vulnerability." This vulnerability is different from those described in CVE-2017-0001, CVE-2017-0025, and CVE-2017-0047.

HighCVSS 7.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2017-0005 is a Windows GDI privilege escalation flaw. An attacker who can run a crafted application locally could gain elevated privileges on affected Windows systems. CISA KEV listing means exploitation has been observed, so exposed legacy Windows assets should be treated as urgent remediation targets.

Executive priority

Prioritize remediation for internet-adjacent, shared, or privileged legacy Windows assets. KEV status makes this more than theoretical, but the local attack requirement means urgency is highest where attackers could already gain user-level execution.

Technical view

Microsoft describes this as a local elevation-of-privilege vulnerability in Windows Graphics Device Interface. CVSS 3.1 is 7.8: local attack vector, low complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on older Windows desktops and servers listed in the CVE, including Vista SP2, Server 2008 variants, Windows 7 SP1, Windows 8.1, Server 2012 variants, Windows RT 8.1, and Windows 10 1507/1511/1607.

Exploitation context

Active exploitation is supported by CISA KEV and Microsoft’s exploit-focused detection and mitigation blog. This is not a remote entry point by itself; it is a post-access privilege escalation path after an attacker can execute code locally.

Researcher notes

The bundle identifies affected Windows versions, CVSS vector, KEV status, and Microsoft references, but does not include exploit mechanics or specific patch KBs. Treat vendor guidance as authoritative for update mapping and detection details.

Mitigation direction

  • Check MSRC guidance for CVE-2017-0005 and apply applicable Microsoft updates.
  • Prioritize affected Windows versions still present in production or privileged environments.
  • Retire, isolate, or tightly restrict unsupported affected operating systems.
  • Review Microsoft MMPC detection guidance for defensive coverage.
  • Limit local code execution opportunities on legacy Windows systems.

Validation and detection

  • Inventory Windows versions and builds against the affected list.
  • Confirm CVE-2017-0005 update status through Microsoft-supported patch reporting.
  • Check EDR and antivirus coverage against Microsoft’s published detection guidance.
  • Review incidents involving local privilege escalation on affected Windows hosts.
  • Validate legacy systems are isolated if updates are unavailable.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-0005 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2017-0005Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Microsoft CorporationWindows GDIThe Graphics Device Interface (GDI) in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; and Windows 10 Gold, 1511, and 1607Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.