Physical privilege escalation through undisclosed protection failure
Published Jun 9, 2021 · Updated Aug 4, 2024
Protection mechanism failure in Intel RealSense ID F450 and F455 allows physically proximate attackers to escalate device privileges. Intel identifies the faulty locus only as a protection mechanism and has not published the operation it performs incorrectly. Physical access and high attack complexity are required, and successful exploitation grants elevated privileges on the device.
Summary
What happened
Protection mechanism failure in Intel RealSense ID F450 and F455 allows physically proximate attackers to escalate device privileges. Intel identifies the faulty locus only as a protection mechanism and has not published the operation it performs incorrectly. Physical access and high attack complexity are required, and successful exploitation grants elevated privileges on the device.
The record
- CVE
- CVE-2020-24515
- Published
- Jun 9, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1068
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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