Code execution via malformed cuobjdump input
Published Apr 22, 2023 · Updated Feb 4, 2025
Out-of-bounds read in NVIDIA CUDA Toolkit before 12.1 Update 1 allows attackers to execute code through a malformed cuobjdump input file. NVIDIA identifies cuobjdump as the affected parser but has not published the exact parsing locus or invalid bounds operation that reads beyond the intended buffer. Exploitation requires tricking a user into running cuobjdump on the file and can also expose limited information or interrupt the tool.
Summary
What happened
Out-of-bounds read in NVIDIA CUDA Toolkit before 12.1 Update 1 allows attackers to execute code through a malformed cuobjdump input file. NVIDIA identifies cuobjdump as the affected parser but has not published the exact parsing locus or invalid bounds operation that reads beyond the intended buffer. Exploitation requires tricking a user into running cuobjdump on the file and can also expose limited information or interrupt the tool.
The record
- CVE
- CVE-2023-25514
- Published
- Apr 22, 2023
- Updated
- Feb 4, 2025
- Vendor
- DPDK Project
- Product
- CUDA Toolkit
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 22, 2023CVE publishedPublication date reported by the CVE source.
- Feb 4, 2025Record 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 prior to 12.1 Update 1
What conditions does exploitation require?
What is affected?
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.
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