# CVE-2009-0584: Integer overflow in n/a

> Integer overflow in ICC library allows attackers to cause denial of service or execute arbitrary code via crafted image files in PostScript or PDF documents.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 23 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-0584, GHSA-3cwm-mjh6-3hwq

## What is CVE-2009-0584?

CVE-2009-0584 is a critical vulnerability in n/a, published on 23 Mar 2009. 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

icc.c in the International Color Consortium (ICC) Format library (aka icclib), as used in Ghostscript 8.64 and earlier and Argyll Color Management System (CMS) 1.0.3 and earlier, allows context-dependent attackers to cause a denial of service (application crash) or possibly execute arbitrary code by using a device file for processing a crafted image file associated with large integer values for certain sizes, related to an ICC profile in a (1) PostScript or (2) PDF file with embedded images.

Weakness: CWE-189

## Which versions are affected by CVE-2009-0584?

It affects 2 products.


Products: Argyllcms Cms, Ghostscript Ghostscript.

## How do I fix CVE-2009-0584?

Upgrade to a fixed version.

## Is CVE-2009-0584 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-4405](https://insights.sbomify.com/CVE-2012-4405/): Integer overflow in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0584 and fix it if it is affected.

What it is: CVE-2009-0584 is a critical vulnerability in n/a, published on 23 Mar 2009. 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-2009-0584 in the wild and no public exploit code.

Affected product: n/a. 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-2009-0584/ (Markdown: https://insights.sbomify.com/CVE-2009-0584/index.md)
```

## Sources

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

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