CVE-2020-13902
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 · uneditedImageMagick 7.0.9-27 through 7.0.10-17 has a heap-based buffer over-read in BlobToStringInfo in MagickCore/string.c during TIFF image decoding.
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 confidenceHeap-based buffer over-read vulnerability in ImageMagick's BlobToStringInfo function in MagickCore/string.c when decoding specially crafted TIFF images. The flaw affects versions 7.0.9-27 through 7.0.10-17 and could allow attackers to read sensitive heap memory contents or cause denial of service via malformed TIFF input.
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.9-27, <= 7.0.10-17CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/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 ImageMagick is installedRun `convert --version` or `magick --version` to check for ImageMagick presence and note the version numberAffected if If the command returns a version number, ImageMagick is installed and the version should be compared to the affected range
-
Compare installed version to affected rangeExamine the version output from the previous step. The affected range is 7.0.9-27 through 7.0.10-17Affected if If the installed version is greater than or equal to 7.0.9-27 and less than or equal to 7.0.10-17, the version is within the vulnerable range
-
Confirm TIFF decoding support is enabledCheck if ImageMagick has TIFF support by running `identify -list configure | grep -i tiff` or by checking for tiff-related delegates in the ImageMagick configurationAffected if If TIFF decoding support is present and enabled, the vulnerability can be triggered by processing a specially crafted TIFF file
You are affected if ImageMagick version 7.0.9-27 through 7.0.10-17 is installed with TIFF decoding support enabled, allowing specially crafted TIFF images to trigger the heap-based buffer over-read in BlobToStringInfo.
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.10-18 or later. Alternatively, disable TIFF decoding support in ImageMagick or implement strict input validation on uploaded TIFF files before processing.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13902 — 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-2020-13902 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