# CVE-2018-16375: Memory corruption in n/a

> A heap-based buffer overflow in OpenJPEG allows attackers to execute arbitrary code or cause denial of service via crafted images.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-16375, ECHO-5c73-4df6-60ac, GHSA-cr53-w8r4-842j, UBUNTU-CVE-2018-16375

## What is CVE-2018-16375?

CVE-2018-16375 is a high-severity memory corruption vulnerability in Uclouvain Openjpeg, published on 3 Sep 2018. 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

An issue was discovered in OpenJPEG 2.3.0. Missing checks for header_info.height and header_info.width in the function pnmtoimage in bin/jpwl/convert.c can lead to a heap-based buffer overflow.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2018-16375?

It affects 1 product.


Products: Uclouvain Openjpeg.

## How do I fix CVE-2018-16375?

Apply the vendor's patch.

## Is CVE-2018-16375 being exploited?

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

What it is: CVE-2018-16375 is a high-severity memory corruption vulnerability in Uclouvain Openjpeg, published on 3 Sep 2018. 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-2018-16375 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-2018-16375/ (Markdown: https://insights.sbomify.com/CVE-2018-16375/index.md)
```

## Sources

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

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