dbcve.org
Nvidia Container ToolkitApplication · Nvidia

CVE-2024-0132

HIGH · 8.3 CVSS v3.1 Published 2024-09-26
Fix available
A fix is available. Upgrade to 1.16.2 / 24.6.2 or later.
See remediation →
90/100
Remediation priority · Urgent
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 Container Toolkit 1.16.1 or earlier contains a Time-of-check Time-of-Use (TOCTOU) vulnerability when used with default configuration where a specifically crafted container image may gain access to the host file system. This does not impact use cases where CDI is used. A successful exploit of this vulnerability may lead to code execution, denial of service, escalation of privileges, information disclosure, 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 confidence

NVIDIA Container Toolkit versions 1.16.1 and earlier contain a Time-of-check Time-of-use (TOCTOU) race condition vulnerability in the default configuration. When CDI (Container Device Interface) is not used, a specially crafted container image can exploit this timing window to escape container isolation and access the host file system, potentially leading to code execution, privilege escalation, or data tampering.

MitigationEnable CDI (Container Device Interface) configuration as an alternative to the default behavior, or upgrade to a version newer than 1.16.1 when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nvidia Container ToolkitApplication
Affected:< 1.16.2
Nvidia Gpu OperatorApplication
Affected:< 24.6.2

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/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. Check NVIDIA Container Toolkit version
    Run 'nvidia-container-toolkit --version' or inspect the installed package (rpm -q nvidia-container-toolkit or dpkg -l nvidia-container-toolkit)
    Affected if Version is present and less than 1.16.2, indicating the toolkit is installed and within the vulnerable range
  2. Check NVIDIA GPU Operator version
    Query the operator via kubectl (kubectl get clusterpolicy -A -o jsonpath='{.items[*].spec.gpu-operator.version}') or check via Operator Lifecycle Manager
    Affected if Version is present and less than 24.6.2, indicating the operator is installed and within the vulnerable range
  3. Verify CDI configuration status
    Inspect the NVIDIA Container Toolkit configuration file (typically at /etc/nvidia-container-runtime/config.toml or in CDI configuration directories under /etc/cdi/) and check whether CDI is enabled
    Affected if CDI is NOT enabled or not configured - the default configuration (CDI disabled) is required for the vulnerability to be exploitable
  4. Confirm default runtime configuration
    Check which container runtime is configured as default (e.g., inspect docker or containerd config for nvidia-container-runtime)
    Affected if The system uses the default nvidia-container-runtime without CDI (the vulnerable default behavior)
  5. Identify if container workloads with GPU images are in use
    Review running containers or recent container image pulls that utilize NVIDIA GPU base images
    Affected if GPU-enabled containers are being run; the vulnerability is triggered when such containers with specially crafted image references are executed

The environment is affected if NVIDIA Container Toolkit version is below 1.16.2 OR GPU Operator version is below 24.6.2, AND CDI is not enabled (the default configuration), and GPU container workloads are present.

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.

dbcve · scoped
Upgrade available Upgrade to 1.16.2 / 24.6.2 or later
Fixed in 1.16.224.6.2
Interim mitigation

Enable CDI (Container Device Interface) configuration as an alternative to the default behavior, or upgrade to a version newer than 1.16.1 when available.

Recommended fix High confidence

Nvidia Container Toolkit 1.16.2 | Nvidia GPU Operator 24.6.2

  1. Check current version of nvidia-container-toolkit installed (e.g., nvidia-container-toolkit --version or rpm -q nvidia-container-toolkit)
  2. Upgrade nvidia-container-toolkit to version 1.16.2 or later using the appropriate package manager (apt/yum/dnf)
  3. For GPU Operator: Check current version (e.g., oc get clusterversion or helm list)
  4. Upgrade GPU Operator to version 24.6.2 or later via Operator Lifecycle Manager (OLM) or helm upgrade
  5. Verify the new versions are installed correctly
  6. Restart container runtime (containerd/docker) if required for changes to take effect
  7. Test that GPU containers still function properly with the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nvidia Container Toolkit 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 the upgrade done

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-0132 — 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-0132 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