Privilege escalation via user-controlled execution-flow changes
Published May 9, 2024 · Updated Aug 1, 2024
Improper privilege management in NVIDIA ChatRTX 0.2.1 and earlier allows local users to escalate privileges through crafted UI input. NVIDIA states that user input sent to the ChatRTX UI changes execution flow improperly but does not identify the affected function or validation error. Low privileges and local access are required; successful exploitation exposes information and permits data tampering, without reported availability impact.
Summary
What happened
Improper privilege management in NVIDIA ChatRTX 0.2.1 and earlier allows local users to escalate privileges through crafted UI input. NVIDIA states that user input sent to the ChatRTX UI changes execution flow improperly but does not identify the affected function or validation error. Low privileges and local access are required; successful exploitation exposes information and permits data tampering, without reported availability impact.
The record
- CVE
- CVE-2024-0096
- Published
- May 9, 2024
- Updated
- Aug 1, 2024
- Vendor
- DPDK Project
- Product
- NVIDIA ChatRTX
- Classifications
- CWE-269, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 9, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.2.1
- Affected versionversion=All versions prior to and including 0.2.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo