dbcve.org
Nvidia Container ToolkitApplication · Nvidia

CVE-2024-0136

HIGH · 8.4 CVSS v3.1 Published 2025-01-28
Fix available
A fix is available. Upgrade to 1.17.3 / 24.9.1 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable

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 contains an improper isolation vulnerability where a specially crafted container image could lead to untrusted code obtaining read and write access to host devices. This vulnerability is present only when the NVIDIA Container Toolkit is configured in a nondefault way. 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 has an improper isolation vulnerability where a malicious container image can bypass isolation boundaries to gain read/write access to host devices. This occurs only in nondefault configurations of the toolkit, potentially allowing attackers to execute code on the host, escalate privileges, or access sensitive data.

MitigationReview and remediate nondefault configurations in NVIDIA Container Toolkit to ensure proper container isolation; avoid running untrusted or unverified container images until the configuration is validated as secure.

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.17.3
Nvidia Gpu OperatorApplication
Affected:< 24.9.1

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
Low
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 `apt list --installed | grep nvidia-container-toolkit` or `rpm -qa | grep nvidia-container-toolkit` depending on your package manager
    Affected if version is lower than 1.17.3 and the toolkit has nondefault configuration settings applied
  2. Check NVIDIA GPU Operator version
    Run `kubectl get csv -n nvidia-gpu-operator` or check the operator deployment version via `helm list -n nvidia-gpu-operator` if Helm was used for installation
    Affected if version is lower than 24.9.1 and the operator uses a nondefault toolkit configuration
  3. Inspect container runtime configuration for NVIDIA hooks
    Review the containerd or docker config files (typically /etc/containerd/config.toml or /etc/docker/daemon.json) for nvidia-container-runtime or nvidia runtime hook configurations that may deviate from vendor defaults
    Affected if custom runtime settings or nonstandard hook configurations are present for GPU containers
  4. Identify nondefault toolkit settings
    Check for environment variables (NVIDIA_VISIBLE_DEVICES, NVIDIA_DRIVER_CAPABILITIES), config files in /etc/nvidia-container-runtime/, or container runtime parameters that override default isolation behavior
    Affected if environment overrides or config files modify the default containment behavior for GPU containers

You are affected if NVIDIA Container Toolkit is below version 1.17.3 or GPU Operator is below version 24.9.1 AND the toolkit has been configured with nondefault settings that deviate from vendor-provided isolation defaults.

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.17.3 / 24.9.1 or later
Fixed in 1.17.324.9.1
Interim mitigation

Review and remediate nondefault configurations in NVIDIA Container Toolkit to ensure proper container isolation; avoid running untrusted or unverified container images until the configuration is validated as secure.

Recommended fix High confidence

Nvidia Container Toolkit >= 1.17.3 OR Nvidia GPU Operator >= 24.9.1

  1. Upgrade NVIDIA Container Toolkit to version 1.17.3 or later by following the installation instructions for your distribution (e.g., package manager or Docker repository)
  2. Upgrade NVIDIA GPU Operator to version 24.9.1 or later using Operator Lifecycle Manager (OLM) or Helm, depending on your Kubernetes deployment method
  3. After upgrading, verify the new versions are installed correctly using 'nvidia-container-cli --version' for the toolkit and checking the operator deployment for GPU Operator
  4. Restart any running containers to ensure they utilize the updated components
Caveat Review release notes for breaking changes between your current version and the target version; test in a non-production environment first

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

Fix this in Nvidia Container Toolkit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0136 — 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-0136 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