# CVE-2017-12596: Memory corruption in n/a

> A crafted image triggers a heap-based buffer over-read in OpenEXR, potentially causing denial of service or other unspecified impacts.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** AZL-69682, AZL-69695, DEBIAN-CVE-2017-12596, GHSA-mrp7-3hfh-25j7, UBUNTU-CVE-2017-12596

## What is CVE-2017-12596?

CVE-2017-12596 is a high-severity memory corruption vulnerability in Openexr Openexr, published on 7 Aug 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In OpenEXR 2.2.0, a crafted image causes a heap-based buffer over-read in the hufDecode function in IlmImf/ImfHuf.cpp during exrmaketiled execution; it may result in denial of service or possibly unspecified other impact.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2017-12596?

It affects 1 product.


Products: Openexr Openexr.

## How do I fix CVE-2017-12596?

Upgrade to a fixed version.

## Is CVE-2017-12596 being exploited?

There is no known exploitation of CVE-2017-12596 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-2017-12596 and fix it if it is affected.

What it is: CVE-2017-12596 is a high-severity memory corruption vulnerability in Openexr Openexr, published on 7 Aug 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-12596 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-2017-12596/ (Markdown: https://insights.sbomify.com/CVE-2017-12596/index.md)
```

## Sources

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

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