CVE-2017-11642
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 · uneditedGraphicsMagick 1.3.26 has a NULL pointer dereference in the WriteMAPImage() function in coders/map.c when processing a non-colormapped image, a different vulnerability than CVE-2017-11638.
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 confidenceGraphicsMagick 1.3.26 contains a NULL pointer dereference vulnerability in the WriteMAPImage() function in coders/map.c. When processing a non-colormapped image, the code attempts to dereference a NULL pointer (likely the colormap), causing a crash or denial of service. This is a classic missing NULL check bug in C code handling edge cases in image format conversion.
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= 1.3.26CVSS 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.0/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.
-
Check installed GraphicsMagick versionRun 'gm -version' or 'identify -version' to determine the installed version of GraphicsMagickAffected if The version shown is exactly 1.3.26
-
Verify MAP image coder is availableRun 'gm identify -list configure' and look for MAP in the list of supported formats, or check if coders/map.c was compiled into the binaryAffected if MAP format support is present in the GraphicsMagick installation
-
Confirm WriteMAPImage function is presentInspect the binary or check for the presence of coders/map.c source file in the buildAffected if The WriteMAPImage function exists in the installation (this is true for all standard GraphicsMagick builds of 1.3.26)
-
Identify image processing workflowsReview any scripts, applications, or services that use GraphicsMagick to process images, particularly those that may convert to MAP format or invoke the WriteMAPImage code pathAffected if The environment processes images through GraphicsMagick where non-colormapped images could be converted to MAP format
You are affected if GraphicsMagick version 1.3.26 is installed AND your system processes images (especially converting to MAP format) where a non-colormapped image could trigger the NULL pointer dereference in WriteMAPImage.
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 dataApply the vendor patch for CVE-2017-11642 which adds proper NULL pointer validation in WriteMAPImage() before dereferencing the colormap. Alternatively, upgrade to GraphicsMagick version 1.3.27 or later which includes the fix.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11642 — 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-2017-11642 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