Nvidia Container Toolkit/GPU Operator up to 1.17.0 improper isolation or compartmentalization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Nvidia Container Toolkit and GPU Operator up to 1.17.0. It has been classified as critical. The affected element is an unknown function. This manipulation causes improper isolation or compartmentalization. This vulnerability appears as CVE-2024-0135. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Nvidia Container Toolkit and GPU Operator up to 1.17.0. It has been declared as critical. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a improper isolation or compartmentalization vulnerability. The CWE definition for the vulnerability is CWE-653. The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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 disclosure, and data tampering.
The advisory is shared at nvidia.custhelp.com. This vulnerability is known as CVE-2024-0135 since 12/02/2023. The exploitation appears to be easy. The attack can be launched remotely. Additional levels of successful authentication are necessary for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 215149 (Fedora 41 : golang-github-nvidia-container-toolkit (2025-a15b07073f)), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Tenable (215149). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.nvidia.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 6.8
VulDB Temp Score: 6.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.6
NVD Vector: 🔍
CNA Base Score: 7.6
CNA Vector (nvidia): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Improper isolation or compartmentalizationCWE: CWE-653
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 215149
Nessus Name: Fedora 41 : golang-github-nvidia-container-toolkit (2025-a15b07073f)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/02/2023 🔍01/28/2025 🔍
01/28/2025 🔍
10/06/2025 🔍
Sources
Vendor: nvidia.comAdvisory: nvidia.custhelp.com
Status: Not defined
CVE: CVE-2024-0135 (🔍)
GCVE (CVE): GCVE-0-2024-0135
GCVE (VulDB): GCVE-100-293893
Entry
Created: 01/28/2025 08:49Updated: 10/06/2025 19:28
Changes: 01/28/2025 08:49 (25), 01/28/2025 08:52 (36), 02/07/2025 16:35 (3), 02/08/2025 09:44 (2), 10/06/2025 19:28 (12)
Complete: 🔍
Committer: mitr
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.