dbcve.org
Debian LinuxOperating system · Debian

CVE-2016-7447

CRITICAL · 9.8 CVSS v3.0 Published 2017-02-06
Fix available
A fix is available. Upgrade to after 1.3.24 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Heap-based buffer overflow in the EscapeParenthesis function in GraphicsMagick before 1.3.25 allows remote attackers to have unspecified impact via unknown vectors.

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

A heap-based buffer overflow vulnerability exists in the EscapeParenthesis function of GraphicsMagick versions prior to 1.3.25, allowing remote attackers to potentially achieve code execution or cause denial of service via unspecified vectors.

MitigationUpgrade GraphicsMagick to version 1.3.25 or later to resolve the heap-based buffer overflow in the EscapeParenthesis function.

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.24
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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 `gm identify -version` to confirm GraphicsMagick is present on the system. On Debian/Ubuntu, also try `dpkg -l | grep -i graphicsmagick`. On openSUSE, try `rpm -qa | grep -i graphicsmagick`.
    Affected if GraphicsMagick is not installed on the system.
  2. Determine the installed version number
    Execute `gm version` and locate the version string in the output. Look for a version number such as 1.3.24, 1.3.23, or earlier.
    Affected if The version displayed is 1.3.24 or any version lower than 1.3.25.
  3. Check for package version on Debian
    If using Debian 8.0, run `apt-cache policy graphicsmagick` to see the installed and available versions of the GraphicsMagick package.
    Affected if The installed version is earlier than 1.3.25.
  4. Check for package version on openSUSE
    On openSUSE 13.2 or Leap 42.1, run `rpm -q GraphicsMagick` to retrieve the installed package version.
    Affected if The RPM package version is earlier than 1.3.25.
  5. Identify if untrusted image processing occurs
    Review any applications or scripts that invoke GraphicsMagick (gm commands) to process images from untrusted sources, as the vulnerability is triggered via image processing operations that invoke the EscapeParenthesis function.
    Affected if GraphicsMagick version is vulnerable AND the system processes untrusted images through gm commands.

A system is affected if GraphicsMagick version 1.3.24 or earlier is installed AND the system processes untrusted image input through GraphicsMagick operations.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.3.24
Interim mitigation

Upgrade GraphicsMagick to version 1.3.25 or later to resolve the heap-based buffer overflow in the EscapeParenthesis function.

Recommended fix High confidence

GraphicsMagick 1.3.25 or later

  1. Check current GraphicsMagick version using `gm version` or `identify -version`
  2. Upgrade GraphicsMagick to version 1.3.25 or later
  3. On Debian 8.0: Run `apt-get update && apt-get upgrade graphicsmagick`
  4. On openSUSE Leap 42.1: Run `zypper update GraphicsMagick`
  5. On openSUSE 13.2: Run `zypper update GraphicsMagick`
  6. Verify the upgrade was successful by checking the version again

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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