NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability which could allow a…
CVE-2024-0126 is a high-severity improper input validation vulnerability in GPU, vGPU, and Cloud Gaming from NVIDIA, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited with local access to the system by an attacker with administrator privileges, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.34% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update gpu_display_driver to 566.03 or 553.24 or 538.95 or 565.57.01, whichever matches your release line, or a later version.
- Update virtual_gpu_manager to 16.8 or 17.4, whichever matches your release line, or a later version.
- Update cloud_gaming_virtual_gpu to 565.57.01 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| NVIDIA | GPU, vGPU, and Cloud Gaming | Not specified in the record | Not stated |
| NVIDIA | gpu_display_driver | 565 up to, but not including, 566.03; 550 up to, but not including, 553.24; 535 up to, but not including, 538.95; 565 up to, but not including, 565.57.01; 550 up to, but not including, 550.127.05; 535 up to, but not including, 535.216.01 | 566.03, 553.24, 538.95, 565.57.01, 550.127.05, 535.216.01 |
| NVIDIA | virtual_gpu_manager | before 16.8; 17.0 up to, but not including, 17.4 | 16.8, 17.4 |
| NVIDIA | cloud_gaming_virtual_gpu | before 565.57.01 | 565.57.01 |
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
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- 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:H/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (nvidia.com).
Official description
NVIDIA GPU Display Driver for Windows and Linux contains a vulnerability which could allow a privileged attacker to escalate permissions. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, and data tampering.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How developers prevent this class of flaw
- Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in GPU, vGPU, and Cloud Gaming
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Recent Improper Input Validation vulnerabilities
- 7.8 High severity
- 9.1 Critical severity
- 8.6 High severity
- 9.2 Critical severity
- 9.8 Critical severity
- 8.1 High severity
Spotted an error? Tell us.