dbcve.org
ImagemagickApplication

CVE-2016-10062

MEDIUM · 5.5 CVSS v3.1 Published 2017-03-02
Fix available
A fix is available. Upgrade to 7.0.1-10 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
The ReadGROUP4Image function in coders/tiff.c in ImageMagick does not check the return value of the fwrite function, which allows remote attackers to cause a denial of service (application crash) 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 confidence

The ReadGROUP4Image function in ImageMagick's TIFF coder calls fwrite() without checking its return value. If fwrite fails (due to disk full, I/O errors, or other issues), the function proceeds as if the write succeeded, leading to incomplete or corrupted data and subsequent application crash when processing crafted TIFF files.

MitigationUpdate ImageMagick to a version where the fwrite return value is properly checked, or implement input validation and file size limits before processing TIFF files to mitigate DoS risk from crafted inputs.

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
ImagemagickApplication
Affected:< 7.0.1-10

CVSS 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed ImageMagick version
    Run 'convert -version' or 'magick -version' to display the installed version information
    Affected if The displayed version is below 7.0.1-10 (e.g., 7.0.1-9, 6.x series, etc.)
  2. Confirm TIFF support is available
    Run 'convert -list configure' or 'identify -list configure' and look for DELEGATES or CODEC entries containing 'tiff'
    Affected if TIFF delegate support is present in the ImageMagick build
  3. Verify TIFF coder is loaded
    Run 'convert -list coder' or 'identify -list coder' and check for the TIFF coder entry
    Affected if The TIFF coder module is listed and available for processing TIFF images
  4. Check ReadGROUP4Image function in TIFF coder
    If source code is available, inspect the TIFF coder source (e.g., coders/tiff.c) for the ReadGROUP4Image function and verify fwrite() return value is checked
    Affected if The function does not check fwrite() return value (vulnerable code pattern present)
  5. Determine TIFF processing usage
    Review application logs or code to identify if ImageMagick processes TIFF files via CLI, API, or delegate libraries
    Affected if The environment processes TIFF files using ImageMagick

Your environment is affected if ImageMagick version is below 7.0.1-10 and TIFF file processing is enabled or used.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 7.0.1-10 or later
Fixed in 7.0.1-10
Interim mitigation

Update ImageMagick to a version where the fwrite return value is properly checked, or implement input validation and file size limits before processing TIFF files to mitigate DoS risk from crafted inputs.

Fix this in Imagemagick Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-10062 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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