CVE-2019-0903: Microsoft GDI Remote Code Execution
Microsoft Graphics Device Interface (GDI) · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-25.
- CVSS v3.1 (CISA ADP)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 22%
- higher than 97.6% of all CVEs
- Added to CISA KEV
- 2022-03-25
- US federal due date 2022-04-15
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2019-0903 explained
CVE-2019-0903 is a remote code execution vulnerability in the Windows Graphics Device Interface (GDI), caused by the way GDI handles objects in memory. It affects many Windows client and server releases. CISA lists it as known to be exploited, so unpatched systems face real risk.
Impact
An attacker who exploits this flaw can run code on the affected system and gain high impact to confidentiality, integrity and availability. The attack can come over the network and needs no privileges or advanced conditions. It does require user interaction. CISA rates the technical impact as total but not automatable, meaning attacks need manual steps per target. Attackers are known to exploit it. Ransomware use is unknown.
Who is affected
The CVE record lists Microsoft Windows releases including 7 for 32-bit Systems Service Pack 1, 8.1 for x64-based systems, RT 8.1, 10 for x64-based Systems and 10 Version 1607 for 32-bit Systems, plus 12 more items. Microsoft Windows Server is affected, with 13 listed models and Core installations such as version 1803 (Core Installation). Windows 10 Version 1903 (32-bit, x64, ARM64) and Windows Server, version 1903 (Server Core installation) are also listed. The CVE record names no fixed version.
Written with AI from the data on this page and checked against it automatically.
Official description
A remote code execution vulnerability exists in the way that the Windows Graphics Device Interface (GDI) handles objects in the memory, aka 'GDI+ Remote Code Execution Vulnerability'.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft WindowsAffectedFixed in
- 7 for 32-bit Systems Service Pack 1
- 7 for x64-based Systems Service Pack 1
- 8.1 for 32-bit systems
- 8.1 for x64-based systems
- RT 8.1
- 10 for 32-bit Systems
- 10 for x64-based Systems
- 10 Version 1607 for 32-bit Systems
- 10 Version 1607 for x64-based Systems
- 10 Version 1703 for 32-bit Systems
- 10 Version 1703 for x64-based Systems
- 10 Version 1709 for 32-bit Systems
- 10 Version 1709 for x64-based Systems
- 10 Version 1803 for 32-bit Systems
- 10 Version 1803 for x64-based Systems
- 10 Version 1803 for ARM64-based Systems
- 10 Version 1809 for 32-bit Systems
- 10 Version 1809 for x64-based Systems
- 10 Version 1809 for ARM64-based Systems
- 10 Version 1709 for ARM64-based Systems
not stated - Microsoft Windows ServerAffectedFixed in
- 13 listed models (2008 for Itanium-Based Systems Service Pack 2 … 2019 (Core installation))
- 2008 R2 for x64-based Systems Service Pack 1 (Core installation)
- 2008 for 32-bit Systems Service Pack 2 (Core installation)
- version 1803 (Core Installation)
- 2008 for x64-based Systems Service Pack 2 (Core installation)
all 13 listed versions
- 2008 for Itanium-Based Systems Service Pack 2
- 2008 for x64-based Systems Service Pack 2
- 2008 for 32-bit Systems Service Pack 2
- 2008 R2 for Itanium-Based Systems Service Pack 1
- 2008 R2 for x64-based Systems Service Pack 1
- 2012
- 2012 (Core installation)
- 2012 R2
- 2012 R2 (Core installation)
- 2016
- 2016 (Core installation)
- 2019
- 2019 (Core installation)
not stated - Microsoft Windows 10 Version 1903 for 32-bit SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1903 for x64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows 10 Version 1903 for ARM64-based SystemsAffected–Fixed innot stated
Affected versions are not specified in the CVE record.
- Microsoft Windows Server, version 1903 (Server Core installation)Affected–Fixed innot stated
Affected versions are not specified in the CVE record.
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows |
| not stated |
| Microsoft Windows Server |
all 13 listed versions
| not stated |
| Microsoft Windows 10 Version 1903 for 32-bit SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1903 for x64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows 10 Version 1903 for ARM64-based SystemsAffected versions are not specified in the CVE record. | – | not stated |
| Microsoft Windows Server, version 1903 (Server Core installation)Affected versions are not specified in the CVE record. | – | not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
- CISA's deadline for US federal agencies: 2022-04-15 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security update for CVE-2019-0903 to all affected Windows and Windows Server systems, following the vendor advisory.
- Prioritize patching, since CISA lists this vulnerability as known to be exploited.
- Upgrade or replace Windows releases that no longer receive security updates.
- Train users to be wary of untrusted content, because exploitation requires user interaction.
- Check systems that stayed unpatched for signs of compromise.
The CVE record names no fixed version. Follow Microsoft's advisory for this CVE, which identifies the security updates for each affected Windows release. CISA's required action is to apply updates per vendor instructions. Until updates are installed, limit user exposure to untrusted content and monitor affected systems.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Questions about CVE-2019-0903
- Is CVE-2019-0903 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-25, with a US federal due date of 2022-04-15. Whether ransomware campaigns use it is unknown.
- Does an attacker need an account on the system?
- No privileges are required, and the attack can come over the network. User interaction is required, though, so a user must take some action for the attack to succeed.
- Which fixed version should I install?
- The CVE record names no fixed version. Use Microsoft's advisory to find the correct security update for each affected Windows or Windows Server release, as CISA's required action directs.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.