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

> Integer overflows in CamlImages allow attackers to execute arbitrary code via crafted GIF or JPEG images with large dimensions.

- **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:** 4 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-2660, DSA-1857-1, GHSA-jv8p-6h4c-vx58

## What is CVE-2009-2660?

CVE-2009-2660 is a medium-severity vulnerability in n/a, published on 4 Aug 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

Multiple integer overflows in CamlImages 2.2 might allow context-dependent attackers to execute arbitrary code via images containing large width and height values that trigger a heap-based buffer overflow, related to (1) crafted GIF files (gifread.c) and (2) crafted JPEG files (jpegread.c), a different vulnerability than CVE-2009-2295.

Weakness: CWE-189

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

It affects 1 product.


Products: Jun Furuse Camlimages.

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

Upgrade to a fixed version.

## Is CVE-2009-2660 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-2295](https://insights.sbomify.com/CVE-2009-2295/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2660 is a medium-severity vulnerability in n/a, published on 4 Aug 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-2660 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-2660/ (Markdown: https://insights.sbomify.com/CVE-2009-2660/index.md)
```

## Sources

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

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