dbcve.org
Debian LinuxOperating system · Debian

CVE-2016-7446

CRITICAL · 9.8 CVSS v3.0 Published 2017-02-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Buffer overflow in the MVG and SVG rendering code in GraphicsMagick 1.3.24 allows remote attackers to have unspecified impact via unknown vectors. Note: This vulnerability exists due to an incomplete patch for CVE-2016-2317.

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

Buffer overflow vulnerability in GraphicsMagick 1.3.24's MVG and SVG rendering code allowing remote code execution. This is an incomplete patch for CVE-2016-2317, indicating the original fix was insufficient to fully address the underlying memory corruption issue.

MitigationUpdate GraphicsMagick to version 1.3.25 or later which contains the complete fix for this vulnerability. Review and test all image processing workflows that handle MVG/SVG 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
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. Confirm GraphicsMagick is installed
    Run 'gm version' or 'graphicsmagick --version' to verify GraphicsMagick is present on the system
    Affected if GraphicsMagick is not installed - the system is not affected by this CVE
  2. Identify installed GraphicsMagick version
    Execute 'gm version' and locate the version number in the output (e.g., GraphicsMagick 1.3.24)
    Affected if Version is exactly 1.3.24 - this is the vulnerable version containing the incomplete patch
  3. Compare version against affected range
    Check if the installed version matches 1.3.24 or falls within the affected versions (GraphicsMagick 1.3.24, Debian 8.0, OpenSUSE 42.1, OpenSUSE 13.2)
    Affected if The installed version is 1.3.24 or matches affected release versions - the system likely contains the vulnerable code
  4. Verify MVG/SVG rendering support is present
    Run 'gm identify -list format' and check for MVG and SVG format support in the output
    Affected if MVG and SVG formats are listed as supported - the vulnerable rendering code paths are available to be triggered
  5. Locate the vulnerable rendering module
    Check for the presence of SVG-related libraries or modules in the GraphicsMagick installation directory (commonly /usr/lib/graphicsmagick or similar)
    Affected if SVG rendering modules are present alongside version 1.3.24 - the specific vulnerable code path exists

A system is affected if GraphicsMagick version 1.3.24 is installed with MVG/SVG rendering support enabled, as this combination contains the incomplete patch for the buffer overflow vulnerability in the rendering code.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update GraphicsMagick to version 1.3.25 or later which contains the complete fix for this vulnerability. Review and test all image processing workflows that handle MVG/SVG input.

Recommended fix Moderate confidence

GraphicsMagick 1.3.25 or later stable release

  1. Check the current GraphicsMagick version using 'gm -version' or your package manager
  2. Update system package lists: 'apt-get update' (Debian) or 'zypper update' (openSUSE)
  3. Upgrade GraphicsMagick: 'apt-get upgrade' (Debian) or 'zypper update' (openSUSE)
  4. Verify the upgrade was successful by checking the installed version
  5. Confirm the new version is 1.3.25 or later which contains the complete patch
Caveat Minor: Some command-line options or API behaviors may have changed between 1.3.24 and 1.3.25; test critical image processing workflows after upgrade

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
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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