msrc.microsoft.com Open in urlscan Pro
2620:1ec:bdf::64  Public Scan

Form analysis
0 forms found in the DOM

Text Content

You need to enable JavaScript to run this app.
Skip to main contentMicrosoft
MSRC
Security Updates
Acknowledgements

Feedback and Support

Sign in to your account
Sign in


We use optional cookies to improve your experience on our websites, such as
through social media connections, and to display personalized advertising based
on your online activity. If you reject optional cookies, only cookies necessary
to provide you the services will be used. You may change your selection by
clicking “Manage Cookies” at the bottom of the page. Privacy Statement
Third-Party Cookies

Accept Reject Manage cookies
 1. MSRC
    MSRC
    
 2. Customer Guidance
    Customer Guidance
    
 3. Security Update Guide
    Security Update Guide
    
 4. Vulnerabilities
    Vulnerabilities
    
 5. CVE 2024 0132
    CVE 2024 0132


NVIDIA: CVE-2024-0132 CONTAINER TOOLKIT 1.16.1 AND EARLIER TIME-OF-CHECK TIME-OF
USE VULNERABILITY NEWRECENTLY UPDATED

On this page
CVE-2024-0132
Subscribe
RSS
PowerShell
API
Security Vulnerability

Released: Oct 9, 2024

Last updated: Oct 23, 2024

Assigning CNA:
NVD

CVE-2024-0132 

Impact: Remote Code Execution

Max Severity: Critical

Weakness:
CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition
CVSS Source: NVD
CVSS:3.1 8.3 / 8.3
Base score metrics: 8.3 / Temporal score metrics: 8.3
Base score metrics: 8.3 / Temporal score metrics: 8.3
Expand all
Collapse all
Metric

Value



Base score metrics(8)
Attack Vector
This metric reflects the context by which vulnerability exploitation is
possible. The Base Score increases the more remote (logically, and physically)
an attacker can be in order to exploit the vulnerable component.
Network
The vulnerable component is bound to the network stack and the set of possible
attackers extends beyond the other options listed, up to and including the
entire Internet. Such a vulnerability is often termed 'remotely exploitable' and
can be thought of as an attack being exploitable at the protocol level one or
more network hops away (e.g., across one or more routers).
Attack Complexity
This metric describes the conditions beyond the attacker’s control that must
exist in order to exploit the vulnerability. Such conditions may require the
collection of more information about the target or computational exceptions. The
assessment of this metric excludes any requirements for user interaction in
order to exploit the vulnerability. If a specific configuration is required for
an attack to succeed, the Base metrics should be scored assuming the vulnerable
component is in that configuration.
High
A successful attack depends on conditions beyond the attacker's control. That
is, a successful attack cannot be accomplished at will, but requires the
attacker to invest in some measurable amount of effort in preparation or
execution against the vulnerable component before a successful attack can be
expected. For example, a successful attack may require an attacker to: gather
knowledge about the environment in which the vulnerable target/component exists;
prepare the target environment to improve exploit reliability; or inject
themselves into the logical network path between the target and the resource
requested by the victim in order to read and/or modify network communications
(e.g., a man in the middle attack).
Privileges Required
This metric describes the level of privileges an attacker must possess before
successfully exploiting the vulnerability.
None
The attacker is unauthorized prior to attack, and therefore does not require any
access to settings or files to carry out an attack.
User Interaction
This metric captures the requirement for a user, other than the attacker, to
participate in the successful compromise the vulnerable component. This metric
determines whether the vulnerability can be exploited solely at the will of the
attacker, or whether a separate user (or user-initiated process) must
participate in some manner.
Required
Successful exploitation of this vulnerability requires a user to take some
action before the vulnerability can be exploited.
Scope
Does a successful attack impact a component other than the vulnerable component?
If so, the Base Score increases and the Confidentiality, Integrity and
Authentication metrics should be scored relative to the impacted component.
Changed
An exploited vulnerability can affect resources beyond the security scope
managed by the security authority of the vulnerable component. In this case, the
vulnerable component and the impacted component are different and managed by
different security authorities.
Confidentiality
This metric measures the impact to the confidentiality of the information
resources managed by a software component due to a successfully exploited
vulnerability. Confidentiality refers to limiting information access and
disclosure to only authorized users, as well as preventing access by, or
disclosure to, unauthorized ones.
High
There is total loss of confidentiality, resulting in all resources within the
impacted component being divulged to the attacker. Alternatively, access to only
some restricted information is obtained, but the disclosed information presents
a direct, serious impact.
Integrity
This metric measures the impact to integrity of a successfully exploited
vulnerability. Integrity refers to the trustworthiness and veracity of
information.
High
There is a total loss of integrity, or a complete loss of protection. For
example, the attacker is able to modify any/all files protected by the impacted
component. Alternatively, only some files can be modified, but malicious
modification would present a direct, serious consequence to the impacted
component.
Availability
This metric measures the impact to the availability of the impacted component
resulting from a successfully exploited vulnerability. It refers to the loss of
availability of the impacted component itself, such as a networked service
(e.g., web, database, email). Since availability refers to the accessibility of
information resources, attacks that consume network bandwidth, processor cycles,
or disk space all impact the availability of an impacted component.
High
There is total loss of availability, resulting in the attacker being able to
fully deny access to resources in the impacted component; this loss is either
sustained (while the attacker continues to deliver the attack) or persistent
(the condition persists even after the attack has completed). Alternatively, the
attacker has the ability to deny some availability, but the loss of availability
presents a direct, serious consequence to the impacted component (e.g., the
attacker cannot disrupt existing connections, but can prevent new connections;
the attacker can repeatedly exploit a vulnerability that, in each instance of a
successful attack, leaks a only small amount of memory, but after repeated
exploitation causes a service to become completely unavailable).

Please see Common Vulnerability Scoring System for more information on the
definition of these metrics.


FAQ

What actions do customers need to take to protect themselves from this
vulnerability?

Customers with Ubuntu Linux or Azure Linux based Azure Kubernetes Service (AKS)
Node Pools using NVIDIA GPU driver configurations are affected by this
vulnerability. Please see below for details on how to update your resources to
be protected against this vulnerability.

 1. Customers with Azure Linux based AKS Node Pool resources must manually
    install AKS Node image version 2024.1009.1 to be protected against this
    vulnerability by running the following CLI command:
    
    tdnf install
    https://packages.microsoft.com/cbl-mariner/2.0/prod/base/x86_64/Packages/n/nvidia-container-toolkit-1.16.2-1.cm2.x86_64.rpm
    
    Note: The AKS node image, version 20241009.1, will be deployed in November
    and contain this package by default. Customers can monitor the status of
    this deployment by using AKS Release Tracker.

 2. Customers with Ubuntu Linux based AKS Node Pool resources must manually
    upgrade the driver version of their AKS Nodes to version 202410.09.0 to be
    protected against this vulnerability by following the guidance here: AKS
    Node Image Upgrade.
    
    Note: This upgrade will not alter your Kubernetes version.


ACKNOWLEDGEMENTS


Microsoft recognizes the efforts of those in the security community who help us
protect customers through coordinated vulnerability disclosure. See
Acknowledgements for more information.


SECURITY UPDATES

To determine the support lifecycle for your software, see the Microsoft Support
Lifecycle.
Updates CVSS
Release date Descending
Edit columns
Download
Filters
Release date

Product

Platform

Impact

Max Severity

Article

Download

Build Number

Oct 9, 2024
Azure Kubernetes Service Node on Ubuntu Linux
-
Remote Code Execution
Critical
 * Release Notes 

 * Security Update 

 * 202410.09.0

Oct 9, 2024
Azure Kubernetes Service Node on Azure Linux
-
Remote Code Execution
Critical
 * Release Notes 

 * Security Update 

 * 20241009.1

Oct 9, 2024
Azure Linux 3.0 x64
-
-
-
 * nvidia-container-toolkit 

 * CBL-Mariner

 * 1.16.2-1

Oct 9, 2024
Azure Linux 3.0 ARM
-
-
-
 * nvidia-container-toolkit 

 * CBL-Mariner

 * 1.16.2-1

Oct 9, 2024
CBL Mariner 2.0 x64
-
-
-
 * nvidia-container-toolkit 

 * CBL-Mariner

 * 1.16.2-1

Oct 9, 2024
CBL Mariner 2.0 ARM
-
-
-
 * nvidia-container-toolkit 

 * CBL-Mariner

 * 1.16.2-1


All results loaded
Loaded all 6 rows


DISCLAIMER

The information provided in the Microsoft Knowledge Base is provided "as is"
without warranty of any kind. Microsoft disclaims all warranties, either express
or implied, including the warranties of merchantability and fitness for a
particular purpose. In no event shall Microsoft Corporation or its suppliers be
liable for any damages whatsoever including direct, indirect, incidental,
consequential, loss of business profits or special damages, even if Microsoft
Corporation or its suppliers have been advised of the possibility of such
damages. Some states do not allow the exclusion or limitation of liability for
consequential or incidental damages so the foregoing limitation may not apply.


REVISIONS

version

revisionDate

description

2.0
Oct 23, 2024

In the Security Updates table, added Azure Kubernetes Service Node on Azure
Linux and Azure Kubernetes Service Node on Ubuntu Linux because these product
are also affected by this vulnerability. Microsoft strongly recommends that
customers using these products install the updates to be fully protected from
the vulnerability.

1.0
Oct 9, 2024

Information published.


How satisfied are you with the MSRC Security Update Guide?
Rating

Broken

Bad

Below average

Average

Great!
