Debian LinuxOperating system · Debian

CVE-2016-7800

HIGH · 7.5 CVSS v3.0 Published 2017-02-06
Fix available
A fix is available. Upgrade to after 1.3.25 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Integer underflow in the parse8BIM function in coders/meta.c in GraphicsMagick 1.3.25 and earlier allows remote attackers to cause a denial of service (application crash) via a crafted 8BIM chunk, which triggers a heap-based buffer overflow.

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 · moderate confidence

Integer underflow in the parse8BIM function in coders/meta.c in GraphicsMagick 1.3.25 and earlier allows remote attackers to cause a denial of service via a crafted 8BIM chunk that triggers a heap-based buffer overflow.

MitigationUpgrade GraphicsMagick to version 1.3.26 or later, or apply vendor patches. Until patched, disable processing of untrusted image files or implement input validation on 8BIM chunk data.

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
Debian LinuxOperating system
Affected:= 8.0
GraphicsmagickApplication
Affected:<= 1.3.25
LeapOperating system
Affected:= 42.1
OpensuseOperating system
Affected:= 13.2

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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. Verify GraphicsMagick is installed
    Run `gm version` or check your package manager (dpkg -l | grep graphicsmagick, rpm -qa | grep graphicsmagick)
    Affected if GraphicsMagick is not installed or the command fails
  2. Determine installed GraphicsMagick version
    Run `gm version` and note the version number displayed (e.g., GraphicsMagick 1.3.x)
    Affected if Version is 1.3.25 or earlier
  3. Confirm the meta coder is available
    Run `gm identify -list configure` and look for 'CODERS' including 'PSD' or check if meta.c is loaded by default (the 8BIM parsing happens in the meta coder)
    Affected if The meta coder or PSD support is built into your installation
  4. Test 8BIM/PSD file processing capability
    Attempt to identify a PSD file using `gm identify <file.psd>` or check coder support via `gm identify -list configure | grep -i psd`
    Affected if PSD/8BIM processing works (indicating the vulnerable code path is present)

You are affected if GraphicsMagick version 1.3.25 or earlier is installed and can process 8BIM/PSD image files.

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 a release after 1.3.25
Interim mitigation

Upgrade GraphicsMagick to version 1.3.26 or later, or apply vendor patches. Until patched, disable processing of untrusted image files or implement input validation on 8BIM chunk data.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-7800 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-7800 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