Service interruption via writable device tree files
Published Jan 26, 2021 · Updated Aug 3, 2024
Improper access control in NVIDIA Jetson L4T before 32.5 allows local users to modify system device tree files and interrupt service. NVIDIA identifies apply_binaries.sh as the locus but has not published which access-control operation or file permissions are incorrect. Low-privilege local access is required; altering the device tree can render the Jetson system unavailable.
Summary
What happened
Improper access control in NVIDIA Jetson L4T before 32.5 allows local users to modify system device tree files and interrupt service. NVIDIA identifies apply_binaries.sh as the locus but has not published which access-control operation or file permissions are incorrect. Low-privilege local access is required; altering the device tree can render the Jetson system unavailable.
The record
- CVE
- CVE-2021-1070
- Published
- Jan 26, 2021
- Updated
- Aug 3, 2024
- Vendor
- NVIDIA
- Product
- NVIDIA Jetson
- Classifications
- T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 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 L4T versions prior to r32.5
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.
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