Cybersecurity researchers have detailed a case of an incomplete patch for a beforehand addressed safety flaw impacting the NVIDIA Container Toolkit that, if efficiently exploited, might put delicate information in danger.
The unique vulnerability CVE-2024-0132 (CVSS rating: 9.0) is a Time-of-Verify Time-of-Use (TOCTOU) vulnerability that might result in a container escape assault and permit for unauthorized entry to the underlying host.
Whereas this flaw was resolved by NVIDIA in September 2024, a brand new evaluation by Pattern Micro has revealed the repair to be incomplete and that there additionally exists a associated efficiency flaw affecting Docker on Linux that might end in a denial-of-service (DoS) situation.
“These points might allow attackers to flee container isolation, entry delicate host assets, and trigger extreme operational disruptions,” Pattern Micro researcher Abdelrahman Esmail said in a brand new report printed right this moment.
The truth that the TOCTOU vulnerability persists signifies that a specifically crafted container might be abused to entry the host file system and execute arbitrary instructions with root privileges. The flaw impacts model 1.17.4 if the characteristic allow-cuda-compat-libs-from-container is explicitly enabled.
“The particular flaw exists inside the mount_files operate,” Pattern Micro said. “The difficulty outcomes from the dearth of correct locking when performing operations on an object. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code within the context of the host.”
Nevertheless, for this privilege escalation to work, the attacker should have already obtained the flexibility to execute code inside a container.
The shortcoming has been assigned the CVE identifier CVE-2025-23359 (CVSS rating: 9.0), which was beforehand flagged by cloud safety agency Wiz as additionally a bypass for CVE-2024-0132 again in February 2025. It has been addressed in model 1.17.4.
The cybersecurity firm mentioned it additionally found a efficiency problem through the evaluation of the CVE-2024-0132 that might probably result in a DoS vulnerability on the host machine. It impacts Docker cases on Linux programs.
“When a brand new container is created with a number of mounts configured utilizing (bind-propagation=shared), a number of mum or dad/little one paths are established. Nevertheless, the related entries usually are not eliminated within the Linux mount desk after container termination,” Esmail mentioned.
“This results in a speedy and uncontrollable progress of the mount desk, exhausting accessible file descriptors (fd). Ultimately, Docker is unable to create new containers as a consequence of fd exhaustion. This excessively massive mount desk results in an enormous efficiency problem, stopping customers from connecting to the host (i.e., through SSH).”
To mitigate the difficulty, it is suggested to observe the Linux mount desk for irregular progress, restrict Docker API entry to licensed personnel, implement sturdy entry management insurance policies, and conduct periodic audits of container-to-host filesystem bindings, quantity mounts, and socket connections.
Source link