CVE-2024-0143
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 · moderate confidenceNVIDIA's nvJPEG2000 library contains an out-of-bounds write vulnerability triggered by specially crafted JPEG2000 files. The vulnerability stems from improper bounds checking during JPEG2000 file parsing, allowing attackers to write beyond allocated memory buffers. Successful exploitation enables arbitrary code execution and potential data manipulation within the affected application's context.
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 filesSearch for nvjpeg2000 shared libraries on the system using 'find /usr -name "*nvjpeg2000*"' or 'ls -la' in common library directoriesAffected if The nvjpeg2000 library files are present on the system
-
Identify the installed nvJPEG2000 versionRun 'nvcc --version' if CUDA toolkit is installed, or check library version strings with 'strings libnvjpeg2000.so | grep -i version', or inspect package manager output for nvidia-nvjpeg2000 packagesAffected if The installed version is earlier than the patched release or cannot be determined to be patched
-
Determine if applications use nvJPEG2000 for processingReview application code or configuration for calls to nvJPEG2000 APIs such as nvjpeg2000DecoderCreate, nvjpeg2000Decode, or similar functions; check process listings for applications linked against nvjpeg2000Affected if Applications or services actively use nvJPEG2000 to decode image data
-
Check for untrusted JPEG2000 input handlingAudit configuration files and application logs for acceptance of JPEG2000 files from external sources, untrusted users, or network endpointsAffected if The system accepts or processes JPEG2000 files from untrusted or external sources without prior validation
A system is affected if it has nvJPEG2000 library installed AND processes untrusted JPEG2000 files with that library, with the specific version being earlier than NVIDIA's patched release.
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 NVIDIA's official patches when released and implement file validation to reject untrusted JPEG2000 input until the library is updated.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0143 — 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-0143 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