dbcve.org
Nvidia Container ToolkitApplication · Nvidia

CVE-2024-0137

MEDIUM · 6.5 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 →
69/100
Remediation priority · Elevated
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 running in the host’s network namespace. 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 denial of service and escalation of privileges.

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

NVIDIA Container Toolkit has an improper isolation vulnerability where a specially crafted container image can execute untrusted code in the host's network namespace, not the container's isolated namespace. This only occurs when the toolkit is configured in a nondefault way, and successful exploitation leads to denial of service and privilege escalation.

MitigationReview and correct the nondefault NVIDIA Container Toolkit configuration to ensure proper container network namespace isolation, or update to a patched version if 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.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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

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 if NVIDIA Container Toolkit is installed
    Run 'nvidia-container-cli --version' or look for the package via 'dpkg -l | grep nvidia-container-toolkit' or 'rpm -qa | grep nvidia-container-toolkit'
    Affected if The package is installed and version is below 1.17.3
  2. Check if NVIDIA GPU Operator is installed
    Run 'kubectl get pods -n nvidia-operator' or check via operator-sdk/helm if operator was deployed, then check operator version with 'kubectl get clusterpolicy -o yaml' or 'helm list -n nvidia-operator'
    Affected if The GPU Operator is installed and version is below 24.9.1
  3. Identify the container runtime configuration
    Examine the NVIDIA container runtime configuration file - typically at /etc/nvidia-container-runtime/config.toml or /etc/nvidia-container-runtime/config.ini - and check for 'no-cgroups' or similar nondefault network isolation settings
    Affected if The configuration contains nondefault settings that disable or override container network namespace isolation (such as host network mode forced on, or cgroup/namespace isolation disabled for networking)
  4. Verify container network isolation is active
    Launch a test container with NVIDIA runtime (nvidia-container-cli or docker run --gpus) and inspect its network namespace with 'ip netns identify <pid>' or 'cat /proc/<pid>/ns/net' compared to the host
    Affected if The container is using the host's network namespace instead of an isolated container network namespace

You are affected if you have NVIDIA Container Toolkit < 1.17.3 or GPU Operator < 24.9.1 AND have configured the toolkit with a nondefault setting that breaks container network namespace isolation.

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 correct the nondefault NVIDIA Container Toolkit configuration to ensure proper container network namespace isolation, or update to a patched version if available.

Recommended fix Moderate confidence

Nvidia Container Toolkit 1.17.3 or Nvidia Gpu Operator 24.9.1

  1. Identify which affected product(s) are in use: Nvidia Container Toolkit, Nvidia Gpu Operator, or both
  2. For Nvidia Container Toolkit: Upgrade to version 1.17.3 or later by following the installation instructions at https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html
  3. For Nvidia Gpu Operator: Upgrade to version 24.9.1 or later by updating the Operator version in your Kubernetes cluster
  4. After upgrade, verify the installation by running `nvidia-container-cli --version` for the toolkit or checking the operator status in the cluster
  5. Review container configurations to ensure the nondefault settings that triggered this vulnerability are still necessary and apply appropriate security principles

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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