Code execution via TegraBoot heap overflow
Published Jun 21, 2021 · Updated Aug 4, 2024
Heap overflow in NVIDIA TegraBoot on Jetson Linux before 32.5.1 allows local users to execute code or interrupt device startup. NVIDIA identifies the bootloader heap as the locus, where an undisclosed operation can overwrite all RAM following the allocated block. Low-privilege local access is required, and successful exploitation can corrupt memory to run code or interrupt service; NVIDIA does not specify whether interruption causes a hang, crash, or reboot.
Summary
What happened
Heap overflow in NVIDIA TegraBoot on Jetson Linux before 32.5.1 allows local users to execute code or interrupt device startup. NVIDIA identifies the bootloader heap as the locus, where an undisclosed operation can overwrite all RAM following the allocated block. Low-privilege local access is required, and successful exploitation can corrupt memory to run code or interrupt service; NVIDIA does not specify whether interruption causes a hang, crash, or reboot.
The record
- CVE
- CVE-2021-34388
- Published
- Jun 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- NVIDIA
- Product
- NVIDIA Jetson
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 21, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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 Jetson Linux versions prior to r32.5.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