CVE-2024-0144
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 a buffer overflow issue by means of a specially crafted JPEG2000 file. A successful exploit of this vulnerability might lead to 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 confidenceThe NVIDIA nvJPEG2000 library contains a buffer overflow vulnerability that can be triggered by processing a specially crafted JPEG2000 file, potentially allowing an attacker to manipulate data.
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 the nvJPEG2000 library on the systemSearch for libnvjpeg2000.so (Linux) or nvjpeg2000.dll (Windows) in common library directories such as /usr/lib, /usr/local/lib, or C:\Windows\System32. Use command: 'find /usr -name "*nvjpeg2000*" 2>/dev/null' on Linux or 'dir /s C:\*nvjpeg2000*' on Windows.Affected if The library file exists on the system, meaning the component is installed.
-
Identify the installed nvJPEG2000 versionRun 'ldd' or check the file properties. On Linux, use 'ls -la' on the library file or check package manager output: 'dpkg -l | grep nvjpeg' or 'rpm -qa | grep nvjpeg'. On Windows, right-click the DLL and select Properties > Details to view the File Version.Affected if The version number is lower than the latest patched version released by NVIDIA for your driver/library package.
-
Determine which applications use nvJPEG2000Review application dependencies using 'ldd <application>' on Linux or Dependency Walker on Windows. Check application logs or documentation to confirm if JPEG2000 decoding via nvJPEG2000 is enabled.Affected if An application on the system links against nvJPEG2000 and processes image files.
-
Check if the system processes untrusted JPEG2000 filesAudit file processing workflows: review application logs, cron jobs, or service configurations that handle image uploads, batch processing, or media ingestion. Look for paths where external JPEG2000 files are submitted for processing.Affected if The system accepts or processes JPEG2000 files from untrusted sources using the nvJPEG2000 library.
If the nvJPEG2000 library is present, the installed version is older than NVIDIA's patched version, and the system processes JPEG2000 files (especially from untrusted sources), the environment is likely affected by CVE-2024-0144.
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 dataUpdate to the latest NVIDIA driver/library version containing the security patch. Until patched, avoid processing untrusted JPEG2000 files with the affected library.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0144 — 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-0144 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