CyberSecBulletin
CVE-2024-0099NVD status: Deferred

vGPU software and Cloud Gaming: Buffer Copy without Checking Size of Input

Published Updated By the CyberSecBulletin desk

CVE-2024-0099 is a high-severity buffer copy without checking size of input vulnerability in vGPU software and Cloud Gaming from NVIDIA, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.21% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update geforce to 555.52.04 or 550.90.07 or 535.183.01 or 470.256.02, whichever matches your release line, or a later version.
  2. Update tesla to 550.90.07 or 535.183.01 or 470.256.02, whichever matches your release line, or a later version.
  3. Update quadro to 555.52.04 or 550.90.07 or 535.183.01 or 470.256.02, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
NVIDIAvGPU software and Cloud GamingNot specified in the recordNot stated
NVIDIAgeforcebefore 555.52.04; before 550.90.07; before 535.183.01; before 470.256.02555.52.04, 550.90.07, 535.183.01, 470.256.02
NVIDIAteslabefore 550.90.07; before 535.183.01; before 470.256.02550.90.07, 535.183.01, 470.256.02
NVIDIAquadrobefore 555.52.04; before 550.90.07; before 535.183.01; before 470.256.02555.52.04, 550.90.07, 535.183.01, 470.256.02
NVIDIArtxbefore 555.52.04; before 550.90.07; before 535.183.01; before 470.256.02555.52.04, 550.90.07, 535.183.01, 470.256.02
NVIDIAnvsbefore 555.52.04; before 550.90.07; before 535.183.01; before 470.256.02555.52.04, 550.90.07, 535.183.01, 470.256.02

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (nvidia.com).

Official description

NVIDIA vGPU software for Linux contains a vulnerability in the Virtual GPU Manager, where the guest OS could cause buffer overrun in the host. A successful exploit of this vulnerability might lead to information disclosure, data tampering, escalation of privileges, and denial of service.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Buffer Copy without Checking Size of Input

The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Buffer Copy without Checking Size of Input vulnerabilities (CWE-120)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in vGPU software and Cloud Gaming

All vGPU software and Cloud Gaming vulnerabilities

Recent Buffer Copy without Checking Size of Input vulnerabilities

Spotted an error? Tell us.