dbcve.org
GraphicsmagickApplication

CVE-2007-0770

HIGH · 9.3 CVSS v2.0 Published 2007-02-12
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 GraphicsMagick and ImageMagick allows user-assisted remote attackers to cause a denial of service and possibly execute arbitrary code via a PALM image that is not properly handled by the ReadPALMImage function in coders/palm.c. NOTE: this issue is due to an incomplete patch for CVE-2006-5456.

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

Buffer overflow vulnerability in the ReadPALMImage function in coders/palm.c in both GraphicsMagick and ImageMagick when processing specially crafted PALM image files, allowing remote attackers to potentially execute arbitrary code or cause denial of service. This is an incomplete fix for CVE-2006-5456.

MitigationUpdate to patched versions of GraphicsMagick and ImageMagick that fully address this vulnerability; if PALM image processing is not required, consider disabling PALM codec support as a defense-in-depth measure.

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:all versions
ImagemagickApplication
Affected:= 6.3.3.4

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. Confirm GraphicsMagick or ImageMagick installation
    Run 'gm -version' for GraphicsMagick or 'identify -version' for ImageMagick to see which product is installed and its version number
    Affected if The installed version is GraphicsMagick any version, or ImageMagick exactly version 6.3.3.4
  2. Locate the PALM codec module
    Search for palm.c or libpalm shared library files in the GraphicsMagick/ImageMagick module directories, typically under /usr/lib/ImageMagick-* or /usr/lib64/ImageMagick-*/modules/coders/
    Affected if The PALM codec module (palm.so or palm.dll) exists in the coders directory, indicating PALM image support is compiled and available
  3. Check PALM support in ImageMagick policy or delegate configuration
    Run 'identify -list configure | grep -i palm' or check /etc/ImageMagick-*/policy.xml for PALM-related entries. Also check delegate.xml for PALM file type handling
    Affected if PALM image format is listed as a supported format or has a delegate configured for processing
  4. Verify active PALM coders in runtime
    Run 'identify -list format' or 'gm identify -list format' and search for 'PALM' in the output to confirm the format is recognized
    Affected if PALM appears in the list of supported image formats, meaning the vulnerable code path can be triggered when processing a malicious PALM file

You are affected if you have GraphicsMagick of any version OR ImageMagick 6.3.3.4 installed, AND the PALM image codec is available and PALM files can be processed.

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 to patched versions of GraphicsMagick and ImageMagick that fully address this vulnerability; if PALM image processing is not required, consider disabling PALM codec support as a defense-in-depth measure.

Recommended fix Moderate confidence

ImageMagick 6.3.5+ or latest 6.x stable; GraphicsMagick: check vendor for fixed release post-2007

  1. Upgrade ImageMagick from version 6.3.3.4 to a newer stable release (6.3.5 or later) that includes the patched coders/palm.c
  2. For GraphicsMagick, check vendor security advisories for the specific patched version addressing CVE-2007-0770
  3. Verify the patch by reviewing the coders/palm.c file in the new version to confirm ReadPALMImage function properly bounds-checks PALM image data
Caveat Minor: ensure any custom PALM image processing workflows still function correctly after upgrade

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

Fix this in Graphicsmagick Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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