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

> Integer overflows in OpenEXR allow attackers to cause crashes or execute code via malicious image files, requiring user interaction to open the file.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 31 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-1720, GHSA-9qfx-pcxp-2cw7

## What is CVE-2009-1720?

CVE-2009-1720 is a high-severity vulnerability in Openexr Openexr, published on 31 Jul 2009. 

### Official description

Multiple integer overflows in OpenEXR 1.2.2 and 1.6.1 allow context-dependent attackers to cause a denial of service (application crash) or possibly execute arbitrary code via unspecified vectors that trigger heap-based buffer overflows, related to (1) the Imf::PreviewImage::PreviewImage function and (2) compressor constructors.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-189

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

It affects 1 product.


Products: Openexr Openexr.

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

Upgrade to a fixed version.

## Is CVE-2009-1720 being exploited?

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

## Other vulnerabilities in Openexr Openexr

- [CVE-2023-5841](https://insights.sbomify.com/CVE-2023-5841/): OpenEXR Heap Overflow in Scanline Deep Data Parsing (critical 9.1)
- [CVE-2026-41142](https://insights.sbomify.com/CVE-2026-41142/): OpenEXR is Vulnerable to Integer overflow in ImageChannel::resize leads to heap OOB write via OpenEXRUtil public API (high 8.8)
- [CVE-2026-42216](https://insights.sbomify.com/CVE-2026-42216/): OpenEXR: Out-of-bounds read in `IDManifest::init()` during prefix expansion (high 8.8)
- [CVE-2017-9111](https://insights.sbomify.com/CVE-2017-9111/): OpenEXR invalid write (high 8.8)
- [CVE-2017-9113](https://insights.sbomify.com/CVE-2017-9113/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1720 is a high-severity vulnerability in Openexr Openexr, published on 31 Jul 2009. 
Exploitation: There is no known exploitation of CVE-2009-1720 in the wild and no public exploit code.

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

## Sources

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

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