CVE-2024-0142
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNVIDIA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceNVIDIA nvJPEG2000 library contains an out-of-bounds write vulnerability that can be triggered by processing a specially crafted JPEG2000 file. The vulnerability allows an attacker to potentially achieve code execution and data tampering through the memory corruption. The attack vector is local (processing a malicious file), requiring user interaction to open the crafted file.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate nvJPEG2000 library installationSearch for the nvJPEG2000 library files on the system. Common file names include nvjpeg2000.dll, libnvjpeg2000.so, or nvjpeg2000.lib. Check typical NVIDIA installation directories such as C:\Program Files\NVIDIA Corporation\ or /usr/local/cuda/lib64/ on Linux systems.Affected if The nvJPEG2000 library is found on the system and no vendor patch has been applied.
-
Determine installed nvJPEG2000 versionRight-click the library file and select Properties, then view the Version tab on Windows. On Linux, use the command: ls -la /usr/local/cuda*/lib64/*nvjpeg2000* or check the NVIDIA driver package version. Also check any software that bundles this library for its version information.Affected if The installed version cannot be verified against a patched version released by NVIDIA, or the version predates the CVE fix date.
-
Identify applications using nvJPEG2000Review installed software that processes image files, particularly CAD applications, medical imaging software, or graphics tools that may leverage NVIDIA GPU acceleration for JPEG2000 decoding. Search process lists for active nvjpeg2000 usage during image processing.Affected if Applications that process JPEG2000 files are installed and utilize the NVIDIA nvJPEG2000 library for decoding.
-
Assess JPEG2000 file processing exposureIdentify whether the system handles untrusted or externally sourced JPEG2000 files. Check file upload directories, email attachments, web-based file converters, or any automated processing pipelines that accept image inputs.Affected if The system processes JPEG2000 files from untrusted sources without verification, or users routinely open JPEG2000 files from unknown origins.
The system is potentially affected if the nvJPEG2000 library is present and processes untrusted JPEG2000 files without confirmation that the library has been patched by NVIDIA.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor patch from NVIDIA to update the nvJPEG2000 library to a patched version. Prioritize updating systems that process untrusted JPEG2000 files.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0142 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data