Debian LinuxOperating system · Debian
CVE-2019-11007
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 · uneditedIn GraphicsMagick 1.4 snapshot-20190322 Q8, there is a heap-based buffer over-read in the ReadMNGImage function of coders/png.c, which allows attackers to cause a denial of service or information disclosure via an image colormap.
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 · high confidenceA heap-based buffer over-read vulnerability exists in GraphicsMagick 1.4 snapshot-20190322 Q8 within the ReadMNGImage function in coders/png.c. When processing specially crafted image files with malicious colormap data, the function reads beyond allocated heap memory boundaries, potentially exposing sensitive memory contents or causing a denial of service.
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 data
Debian LinuxOperating system
= 8.0= 9.0= 10.0
Ubuntu LinuxOperating system
= 18.04<= 1.3.31= 15.0= 15.0= 42.3CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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.
-
Verify GraphicsMagick is installedRun `gm version` or `which gm` to confirm GraphicsMagick is present on the systemAffected if GraphicsMagick is not installed - the system is not affected by this CVE
-
Check the installed GraphicsMagick versionRun `gm version` and examine the version number in the output. Compare it against the affected range: GraphicsMagick <= 1.3.31Affected if The installed version is 1.3.31 or lower, or the version cannot be determined but is known to be <= 1.3.31
-
Confirm MNG image support is enabledRun `gm identify -list format` and look for MNG in the output, or check the configuration with `gm -list configure` for MNG supportAffected if MNG format support is enabled - the vulnerable ReadMNGImage function can be invoked
-
Verify PNG coder is loadedCheck that the PNG coder module is available: run `gm identify -list configure` or inspect the coders/png.c file presence in the installationAffected if The PNG coder is present and loaded - the vulnerable code path exists
-
Check for processing of untrusted MNG/PNG filesReview application logs, file upload directories, or image processing pipelines that accept MNG or PNG files from untrusted sourcesAffected if The system processes MNG or PNG files from untrusted or external sources without prior validation
A system is affected if it runs GraphicsMagick version 1.3.31 or earlier with MNG and PNG support enabled, and processes untrusted image files.
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.
From vendor dataUpdate GraphicsMagick to a version that includes the patched bounds checking in the ReadMNGImage function, or implement input validation to reject untrusted MNG/PNG files before processing.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11007 — 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-11007 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