CVE-2019-0903
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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'.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA remote code execution vulnerability exists in Windows GDI+ (Graphics Device Interface) due to improper memory handling when processing graphic objects. An attacker could exploit this by tricking a user into opening specially crafted content (e.g., malicious image files) to execute arbitrary code in the context of the current user.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Windows versionRun 'winver' from the command prompt or check System Properties, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'Affected if The reported version matches Windows 10 1507, 1607, 1703, 1709, 1803, 1809, 1903, or Windows 7 (any version)
-
Confirm build number for Windows 10Run 'winver' or 'systeminfo' and note the build number displayed (e.g., 1507, 1607, 1703, etc.)Affected if The build falls within versions 1507 through 1903 inclusive (all builds within these version ranges are affected)
-
Verify GDI+ component presenceGDI+ (gdiplus.dll) is a core Windows graphics subsystem present by default. Check existence at %SystemRoot%\System32\gdiplus.dllAffected if The file exists (it will exist on any standard Windows installation, this confirms the vulnerable component is present)
If the system runs Windows 10 versions 1507 through 1903 or Windows 7 any version, and the GDI+ component is present, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the Microsoft security update KB4505057 (or subsequent cumulative updates) to all affected Windows systems. Prioritize workstations and systems that process untrusted graphic content.
- Open Windows Update by clicking the Start button and selecting Settings > Update & Security > Windows Update
- Click 'Check for updates' to ensure you have the latest updates
- Install the July 2019 security updates from Microsoft which address this vulnerability
- Alternatively, manually download and install the appropriate security update for your Windows version from the Microsoft Update Catalog
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0903 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-0903 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data