Debian LinuxOperating system · Debian
CVE-2016-7448
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 · uneditedThe Utah RLE reader in GraphicsMagick before 1.3.25 allows remote attackers to cause a denial of service (CPU consumption or large memory allocations) via vectors involving the header information and the file size.
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 confidenceThe Utah RLE (Run-Length Encoding) image reader in GraphicsMagick versions prior to 1.3.25 contains a vulnerability where specially crafted header information combined with manipulated file size values triggers excessive CPU consumption or attempts to allocate very large memory blocks, leading to denial of service conditions.
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
= 8.0<= 1.3.24= 42.1= 13.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm GraphicsMagick installation and versionRun `gm version` or `graphicsmagick --version` to obtain the installed GraphicsMagick version numberAffected if The version reported is 1.3.24 or earlier
-
Verify RLE coder module availabilityRun `gm identify -list format` and look for RLE in the list of supported formats, or check for a coder file named 'coder_rle.so' or 'rle.c' in the coders directory (commonly /usr/lib/GraphicsMagick-*/coders/)Affected if RLE format support is listed and the RLE coder module exists on the system
-
Confirm the Utah RLE reader is in useThe vulnerability exists specifically in the Utah RLE reader component; GraphicsMagick uses format-specific coders located in the coders directoryAffected if The RLE coder is present and can be invoked when processing RLE format images
-
Test RLE image processing capabilityAttempt to identify a sample RLE image file using `gm identify <image.rle>` if an RLE test file is available, or check that the RLE format is recognizedAffected if GraphicsMagick successfully processes or recognizes RLE format images
You are affected if GraphicsMagick version 1.3.24 or earlier is installed AND the RLE format coder/reader module is available and functional on your system.
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 GraphicsMagick to version 1.3.25 or later to obtain the vendor patch addressing this issue in the Utah RLE reader.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-7448 — 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-2016-7448 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