dbcve.org
GraphicsmagickApplication

CVE-2008-6070

HIGH · 9.3 CVSS v2.0 Published 2009-02-10
Fix available
A fix is available. Upgrade to after 1.2.2 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
Multiple heap-based buffer underflows in the ReadPALMImage function in coders/palm.c in GraphicsMagick before 1.2.3 allow remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted PALM image, a different vulnerability than CVE-2007-0770. NOTE: some of these details are obtained from third party information.

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

Heap-based buffer underflow vulnerabilities in GraphicsMagick's PALM image parser (coders/palm.c, ReadPALMImage function) allow remote attackers to write before the start of allocated heap buffers via crafted PALM images, potentially enabling arbitrary code execution or denial of service.

MitigationUpdate GraphicsMagick to version 1.2.3 or later to obtain the patched code. If immediate patching is not feasible, disable PALM image format support or restrict image processing to trusted sources.

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
GraphicsmagickApplication
Affected:<= 1.2.2= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.1= 1.1.1= 1.1.2= 1.1.3

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 'graphicsmagick --version' to confirm GraphicsMagick is present on the system
    Affected if GraphicsMagick is not installed or the command fails
  2. Identify the installed GraphicsMagick version
    Run 'gm version' and examine the output for the version number (e.g., 1.2, 1.1.3, 1.0.6)
    Affected if The installed version is 1.2.2 or earlier, or matches any of: 1.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.1, 1.1.1, 1.1.2, 1.1.3, or any version up to and including 1.2.2
  3. Confirm PALM image format support is available
    Run 'gm identify -list format' and look for 'PALM' in the output, or check if coders/palm.c is present in the GraphicsMagick installation directory
    Affected if PALM format support is present and the module can be loaded
  4. Check if PALM files can be processed
    Attempt to identify a sample PALM image file using 'gm identify <file.palm>' or process one using 'gm convert <file.palm> output.png'
    Affected if The PALM image is processed without errors, confirming the vulnerable parser code path is reachable

A user is affected if GraphicsMagick version 1.2.2 or earlier (including all 1.0.x and 1.1.x releases) is installed and the PALM image format parser is accessible and functional on the system.

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.2.2
Interim mitigation

Update GraphicsMagick to version 1.2.3 or later to obtain the patched code. If immediate patching is not feasible, disable PALM image format support or restrict image processing to trusted sources.

Recommended fix High confidence

GraphicsMagick 1.2.3 or later

  1. Check current GraphicsMagick version using 'gm version' or your system's package manager
  2. Download GraphicsMagick 1.2.3 or later from the official GraphicsMagick distribution (www.graphicsmagick.org)
  3. If using source compilation, download and compile the fixed version: ./configure, make, make install
  4. If using a package manager (apt, yum, brew, etc.), upgrade to the available package version that includes the 1.2.3 fix or later
  5. Verify the installation succeeded and the version is at least 1.2.3 using 'gm version'
  6. Test that GraphicsMagick processes images normally to confirm the upgrade did not break functionality

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

Fix this in Graphicsmagick Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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