CVE-2017-11724
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 · uneditedThe ReadMATImage function in coders/mat.c in ImageMagick through 6.9.9-3 and 7.x through 7.0.6-3 has memory leaks involving the quantum_info and clone_info data structures.
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 confidenceMemory leak vulnerability in ImageMagick's ReadMATImage function (coders/mat.c) where quantum_info and clone_info data structures are not properly deallocated during MAT image file processing, leading to memory exhaustion when processing specially crafted MAT image files.
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= 6.9.9-3= 7.0.1-0= 7.0.1-1= 7.0.1-2= 7.0.1-3= 7.0.1-4= 7.0.1-5= 7.0.1-6= 7.0.1-7= 7.0.1-8= 7.0.1-10= 7.0.2-0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Identify installed ImageMagick versionRun 'convert -version' (ImageMagick 6) or 'magick -version' (ImageMagick 7) and note the version number in the outputAffected if The version matches exactly: 6.9.9-3, 7.0.1-0, 7.0.1-1, 7.0.1-2, 7.0.1-3, 7.0.1-4, 7.0.1-5, 7.0.1-6, 7.0.1-7, 7.0.1-8, 7.0.1-10, or 7.0.2-0
-
Verify MAT image coder availabilityRun 'convert -list configure | grep -i mat' (ImageMagick 6) or 'magick -list configure | grep -i mat' (ImageMagick 7) to check if MAT support is compiled inAffected if MAT coder is listed as supported (indicates the vulnerable code path can be triggered)
-
Check for MAT file processing in logs or applicationsReview application logs, web server logs, or file processing records for .mat file imports using ImageMagick (look for files with .mat extension processed by convert/magick)Affected if ImageMagick is used to process MAT image files from untrusted sources
-
Verify source code fix status (if using source build)Inspect coders/mat.c in the ImageMagick source tree: search for 'quantum_info' and 'clone_info' to confirm proper deallocation (memory free calls) before all return paths in ReadMATImage functionAffected if The source code lacks proper memory free calls for quantum_info and clone_info before function return
-
Monitor memory usage during MAT image processingProcess a test MAT image file while monitoring memory consumption (use tools like 'top', 'htop', or process memory profiling) to observe abnormal memory growthAffected if Memory continuously increases without release during MAT file processing, indicating the leak is active
You are affected if your installed ImageMagick version exactly matches one of the listed vulnerable versions AND the MAT image coder is enabled and used to process MAT 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 dataUpgrade ImageMagick to version 7.0.7-0 or later which contains the fix, or apply a patch to coders/mat.c ensuring quantum_info and clone_info memory allocations are properly freed before function return.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11724 — 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-11724 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