Exploited CVEs / Microsoft / CVE-2017-0001
CVE-2017-0001
Microsoft Graphics Device Interface (GDI) Privilege Escalation Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2022-03-24 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Microsoft Security Update Guide (MSRC), linked below.
Risk summary
Actively exploited Microsoft Graphics Device Interface (GDI) vulnerability. Added to the CISA KEV catalog 2022-03-03.
Senserva AI Opinion for CVE-2017-0001
The affected platform list is what stands out here: Windows Vista SP2, Server 2008, Windows 7 SP1, 8.1, RT 8.1, Server 2012, and Windows 10 through 1607 all carry this GDI privilege escalation, so it maps almost exactly onto any legacy Windows estate. A local user gains elevated privileges, Severity is High, and exploitation is confirmed (KEV 2022-03-03). Those older OS versions are also past or near end of support.
Do this: Locate remaining Vista, 2008, 7, and 2012 systems, patch what you can, and plan migrations for what you cannot.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2017-0001
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2017-0001
- Published
- 2022-03-03
- Last revised
- 2022-03-03
- Changes tracked
- 1
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
CISA required action
Federal remediation due date: 2022-03-24 (past due).
Official fix for CVE-2017-0001
The authoritative fix and affected-version list are published by the vendor. Find the Graphics Device Interface (GDI) advisory on Microsoft Security Update Guide (MSRC).
Common questions about CVE-2017-0001
Is CVE-2017-0001 actively exploited?
Yes. CVE-2017-0001 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2022-03-03, which means exploitation in the wild has been confirmed, not predicted.
What is the CISA deadline and required action for CVE-2017-0001?
CISA set the federal remediation due date at 2022-03-24, which has passed; treat any unremediated system as overdue.
What fixes CVE-2017-0001?
The authoritative fix is in the vendor advisory: see Microsoft Security Update Guide (MSRC) for the patched Graphics Device Interface (GDI) versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2017-0001?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2017-0001's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (morning and afternoon US Central).
Scope and sources
- More exploited Microsoft CVEs
- CVE-2019-1068CVE-2008-4250CVE-2009-1537CVE-2010-0249CVE-2010-0806CVE-2026-41091CVE-2026-45498CVE-2026-33825
All Microsoft exploited CVEs on one page: Microsoft vulnerabilities actively exploited.
- Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.