# CVE-2008-1097: Memory corruption in n/a

> Heap-based buffer overflow in ImageMagick and GraphicsMagick allows remote attackers to execute arbitrary code or cause a crash via a crafted PCX file.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-1097, GHSA-w4vc-7rfv-99f6

## What is CVE-2008-1097?

CVE-2008-1097 is a medium-severity memory corruption vulnerability in Imagemagick Imagemagick, published on 5 Mar 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Heap-based buffer overflow in the ReadPCXImage function in the PCX coder in coders/pcx.c in (1) ImageMagick 6.2.4-5 and 6.2.8-0 and (2) GraphicsMagick (aka gm) 1.1.7 allows user-assisted remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted .pcx file that triggers incorrect memory allocation for the scanline array, leading to memory corruption.

Weakness: CWE-399

## Which versions are affected by CVE-2008-1097?

It affects 2 products.


Products: Imagemagick Graphicsmagick, Imagemagick Imagemagick.

## How do I fix CVE-2008-1097?

Upgrade to a fixed version.

## Is CVE-2008-1097 being exploited?

There is no known exploitation of CVE-2008-1097 in the wild and no public exploit code.

## Other vulnerabilities in Imagemagick Imagemagick

- [CVE-2008-1096](https://insights.sbomify.com/CVE-2008-1096/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1097 and fix it if it is affected.

What it is: CVE-2008-1097 is a medium-severity memory corruption vulnerability in Imagemagick Imagemagick, published on 5 Mar 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-1097 in the wild and no public exploit code.

Affected product: Imagemagick Imagemagick. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2008-1097/ (Markdown: https://insights.sbomify.com/CVE-2008-1097/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2008-1097
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-1097
- OSV: https://osv.dev/vulnerability/CVE-2008-1097

---
From sbomify Insights: https://insights.sbomify.com/CVE-2008-1097/
Summaries are generated and may contain mistakes; the official description above is the record.