# CVE-2024-0143: Memory corruption in nvJPEG2000

> An attacker can achieve code execution and data tampering via a crafted JPEG2000 file exploiting an out-of-bounds write in the NVIDIA nvJPEG2000 library.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/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:** No
- **Published:** 12 Feb 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-cx98-f2vw-wvr8

## What is CVE-2024-0143?

CVE-2024-0143 is a medium-severity memory corruption vulnerability in NVIDIA nvJPEG2000, published on 12 Feb 2025. 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

NVIDIA nvJPEG2000 library contains a vulnerability where an attacker can cause an out-of-bounds write issue by means of a specially crafted JPEG2000 file. A successful exploit of this vulnerability might lead to code execution and data tampering.

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

## Which versions are affected by CVE-2024-0143?


## How do I fix CVE-2024-0143?

No fix has been published for CVE-2024-0143 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-0143 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0143 and fix it if it is affected.

What it is: CVE-2024-0143 is a medium-severity memory corruption vulnerability in NVIDIA nvJPEG2000, published on 12 Feb 2025. 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-2024-0143 in the wild and no public exploit code.

Affected product: NVIDIA nvJPEG2000. 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-2024-0143/ (Markdown: https://insights.sbomify.com/CVE-2024-0143/index.md)
```

## Sources

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

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