CVE-2024-0135
Nvidia Container Toolkit ≤ 1.17.3
Raw vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:HSummary
CVE-2024-0135 is a high-severity Improper Isolation or Compartmentalization (CWE-653) vulnerability in Nvidia Nvidia Container Toolkit. Its CVSS base score is 7.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Escape to Host (T1611); ranked in the top 37% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-2 (Separation of System and User Functionality) and SC-3 (Security Function Isolation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-0135 is an improper isolation vulnerability in the NVIDIA Container Toolkit. The issue arises when a specially crafted container image can lead to modification of a host binary. Successful exploitation may result in code execution, denial of service, escalation of privileges, information disclosure, and data tampering. The vulnerability is rated with a CVSS v3.1 base score of 7.6 (AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H) and is associated with CWE-653.
An attacker requires high privileges (PR:H) on the target system and must convince a user to interact with a malicious container image (UI:R), such as loading or running it. The attack is feasible over the network (AV:N) but involves high complexity (AC:H). Exploitation changes the scope (S:C) and can achieve high impacts on confidentiality, integrity, and availability, including arbitrary code execution on the host and privilege escalation beyond the container's isolation.
NVIDIA has published a security advisory at https://nvidia.custhelp.com/app/answers/detail/a_id/5599 detailing the vulnerability, which was disclosed on 2025-01-28. Practitioners should consult this advisory for patch information and mitigation guidance.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-15934
Vulnerability Data
NVIDIA Container Toolkit contains an improper isolation vulnerability where a specially crafted container image could lead to modification of a host binary. A successful exploit of this vulnerability may lead to code execution, denial of service, escalation of privileges, information…
more
disclosure, and data tampering.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 8 hardening rules · 7 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Security function isolation is the canonical mechanism for protecting higher-privilege compartments.
Process isolation maintains separate execution domains so one process cannot affect another’s privilege level.
Explicit separation of user and management functionality implements the required compartmentalization.
System partitioning creates distinct domains that enforce isolation between differently privileged components.
Access enforcement directly requires approved authorizations to be applied to compartmentalized resources.
Information flow enforcement structurally prevents unauthorized mixing of data or functions across privilege boundaries.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Segregation of duties directly enforces separation of privilege levels and functions.
Network segregation is a classic technical control for isolating different privilege domains.
Secure system architecture principles explicitly call for isolation and least-privilege boundaries.
Separation of development, test and production environments is a direct application of compartmentalization.
Access control policies establish the boundaries that isolation must enforce.
Managing access rights is the operational mechanism for compartmentalizing privileges.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 9 (1 rule)
- V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-653
RHEL 9 (2 rules)
- V-258078 RHEL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-653
- V-272496 RHEL 9 must elevate the SELinux context when an administrator calls the sudo command. prevents CWE-653
Windows 10 (1 rule)
- V-220712 Only accounts responsible for the administration of a system must have Administrator rights on the system. prevents CWE-653
Windows 11 (1 rule)
- V-253269 Only accounts responsible for the administration of a system must have Administrator rights on the system. prevents CWE-653
Windows Server 2016 (1 rule)
- V-225007 Only administrators responsible for the member server or standalone or nondomain-joined system must have Administrator rights on the system. prevents CWE-653