# CVE-2016-8332: Memory corruption in OPENJPEG

> A buffer overflow in OpenJPEG allows arbitrary code execution when a user opens a malicious JPEG2000 image, often embedded in PDFs.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 28 Oct 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-8332, GHSA-qxqh-jjhc-4wfg, UBUNTU-CVE-2016-8332

## What is CVE-2016-8332?

CVE-2016-8332 is a high-severity memory corruption vulnerability in Uclouvain Openjpeg, published on 28 Oct 2016. 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

A buffer overflow in OpenJPEG 2.1.1 causes arbitrary code execution when parsing a crafted image. An exploitable code execution vulnerability exists in the jpeg2000 image file format parser as implemented in the OpenJpeg library. A specially crafted jpeg2000 file can cause an out of bound heap write resulting in heap corruption leading to arbitrary code execution. For a successful attack, the target user needs to open a malicious jpeg2000 file. The jpeg2000 image file format is mostly used for embedding images inside PDF documents and the OpenJpeg library is used by a number of popular PDF renderers making PDF documents a likely attack vector.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2016-8332?

It affects 1 product.


Products: Uclouvain Openjpeg.

## How do I fix CVE-2016-8332?

Upgrade to a fixed version.

## Is CVE-2016-8332 being exploited?

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

## Other vulnerabilities in Uclouvain Openjpeg

- [CVE-2013-4289](https://insights.sbomify.com/CVE-2013-4289/): Integer overflow in n/a (critical 10.0)
- [CVE-2013-4290](https://insights.sbomify.com/CVE-2013-4290/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-3358](https://insights.sbomify.com/CVE-2012-3358/): Memory corruption in n/a (critical 10.0)
- [CVE-2018-7648](https://insights.sbomify.com/CVE-2018-7648/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-17479](https://insights.sbomify.com/CVE-2017-17479/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-8332 and fix it if it is affected.

What it is: CVE-2016-8332 is a high-severity memory corruption vulnerability in Uclouvain Openjpeg, published on 28 Oct 2016. 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-2016-8332 in the wild and no public exploit code.

Affected product: Uclouvain Openjpeg. 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-2016-8332/ (Markdown: https://insights.sbomify.com/CVE-2016-8332/index.md)
```

## Sources

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

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