dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2024-0145

MEDIUM · 6.8 CVSS v3.1 Published 2025-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
NVIDIA nvJPEG2000 library contains a vulnerability where an attacker can cause a heap-based buffer overflow 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 confidence

The NVIDIA nvJPEG2000 library contains a heap-based buffer overflow vulnerability that can be triggered by a specially crafted JPEG2000 file. When processing a maliciously constructed image, the library writes data beyond the allocated heap buffer, potentially allowing an attacker to execute arbitrary code or tamper with data. This is a memory corruption vulnerability in a graphics processing library.

MitigationUpdate the NVIDIA nvJPEG2000 library to the latest patched version provided by NVIDIA. Until the patch is applied, avoid processing untrusted or unknown JPEG2000 files with the affected library.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the nvJPEG2000 library on the system
    Search for the library file using 'find /usr -name "*nvjpeg*" -o -name "*nvJPEG*"' or check common NVIDIA driver/library installation directories such as /usr/lib, /usr/local/lib, or the NVIDIA CUDA library path.
    Affected if The library file is present on the system, meaning nvJPEG2000 is installed.
  2. Identify the installed nvJPEG200 version
    Run 'nvcc --version' if CUDA is installed, or check the library file version using 'strings <library_path> | grep -i version' or 'file <library_path>'. Also check the NVIDIA driver package version via 'nvidia-smi' or package manager.
    Affected if The installed version is older than the patched version released by NVIDIA for this CVE.
  3. Determine if applications use nvJPEG2000 for image processing
    Review any applications that process JPEG2000 images, particularly graphics tools, image converters, or services that handle image uploads. Search application logs or code for nvJPEG2000 API usage.
    Affected if Applications or services actively use nvJPEG2000 to decode or process JPEG2000 image files.
  4. Check for processing of untrusted or user-uploaded JPEG2000 files
    Audit workflows where external or untrusted JPEG2000 images are processed. Review web applications, file upload handlers, image processing pipelines, or any system accepting image input from users or external sources.
    Affected if The system processes JPEG2000 files from untrusted or unknown sources without prior validation.
  5. Review environment variables and library loading paths
    Check LD_LIBRARY_PATH and other library path configurations to see which nvJPEG2000 version gets loaded at runtime. Use 'ldd <application>' to trace which library version an application links against.
    Affected if An older vulnerable version of nvJPEG2000 is loaded at runtime by critical applications.

You are affected if the nvJPEG2000 library is installed and its version is lower than the patched version, AND your system processes or could process JPEG2000 files (especially from untrusted sources) using this library.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the NVIDIA nvJPEG2000 library to the latest patched version provided by NVIDIA. Until the patch is applied, avoid processing untrusted or unknown JPEG2000 files with the affected library.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0145 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-0145 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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