CVE-2017-13062
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 ImageMagick 7.0.6-6, a memory leak vulnerability was found in the function formatIPTC in coders/meta.c, which allows attackers to cause a denial of service (WriteMETAImage memory consumption) via a crafted file.
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 memory leak exists in ImageMagick 7.0.6-6 in the formatIPTC function within coders/meta.c. When processing a crafted image file containing specially crafted IPTC metadata, memory is allocated but not properly freed, leading to progressive memory consumption that can exhaust system resources and cause 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= 7.0.6-6CVSS 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' or 'magick -version' to retrieve the installed version numberAffected if The version displayed is exactly 7.0.6-6, as this is the only affected version listed in the CVE details
-
Confirm ImageMagick is present on the systemRun 'which convert' or 'which magick' to verify the ImageMagick binary existsAffected if ImageMagick is installed and the version check returns 7.0.6-6
-
Check if IPTC metadata processing is enabledRun 'convert -list configure | grep DELEGATES' or inspect /etc/ImageMagick-6/policy.xml (or similar config) to see if image format delegates including those capable of IPTC handling are enabledAffected if ImageMagick can process image formats that may contain IPTC metadata (JPEG, TIFF, etc.) and no policy restrictions are in place to block such processing
-
Determine if user processes untrusted image filesReview application logs, web server access logs, or file upload processing directories to identify if ImageMagick is being used to process images from external or untrusted sourcesAffected if ImageMagick is actively processing image files, especially those from untrusted sources, which could trigger the vulnerability if the files contain crafted IPTC metadata
A user is affected if ImageMagick version 7.0.6-6 is installed and is used to process image files containing IPTC metadata, with no resource limits configured to constrain memory consumption.
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 ImageMagick to a version that includes the fix for this vulnerability. Additionally, implement resource limits on ImageMagick processing and validate/sanitize uploaded image files before processing.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13062 — 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-13062 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