Crash or output tampering via malformed ELF
Published Aug 31, 2024 · Updated Sep 3, 2024
Improper input validation in NVIDIA CUDA Toolkit 12.6 and earlier allows local users to crash cuobjdump or alter its output via malformed ELF files. The cuobjdump command fails to validate a specified quantity while parsing an ELF file, causing a crash or incorrect output. Execution requires a user to run cuobjdump on attacker-supplied local input; effects remain within the unprivileged process.
Summary
What happened
Improper input validation in NVIDIA CUDA Toolkit 12.6 and earlier allows local users to crash cuobjdump or alter its output via malformed ELF files. The cuobjdump command fails to validate a specified quantity while parsing an ELF file, causing a crash or incorrect output. Execution requires a user to run cuobjdump on attacker-supplied local input; effects remain within the unprivileged process.
The record
- CVE
- CVE-2024-0111
- Published
- Aug 31, 2024
- Updated
- Sep 3, 2024
- Vendor
- DPDK Project
- Product
- CUDA Toolkit
- Classifications
- CWE-1284, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 31, 2024CVE publishedPublication date reported by the CVE source.
- Sep 3, 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=All versions up to and including CUDA Toolkit 12.6
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