Boot-block bypass via stale tamper reset state
Published Aug 29, 2024 · Updated Aug 30, 2024
Improper tamper-event handling in Silicon Labs SE Firmware 2.2.5 and earlier allows physically proximate attackers to bypass boot blocking. The firmware does not reliably update the TAMPERRSTCAUSE register after a level 4 tamper reset, so consecutive resets are not counted as configured. Physical access to an affected xG23B, xG24B, xG25B, or xG28B HSE-SVH device is required, and the consequence is limited to defeating the configured boot-attempt block.
Summary
What happened
Improper tamper-event handling in Silicon Labs SE Firmware 2.2.5 and earlier allows physically proximate attackers to bypass boot blocking. The firmware does not reliably update the TAMPERRSTCAUSE register after a level 4 tamper reset, so consecutive resets are not counted as configured. Physical access to an affected xG23B, xG24B, xG25B, or xG28B HSE-SVH device is required, and the consequence is limited to defeating the configured boot-attempt block.
The record
- CVE
- CVE-2024-2502
- Published
- Aug 29, 2024
- Updated
- Aug 30, 2024
- Vendor
- Silicon Laboratories
- Product
- Secure Element Firmware
- Classifications
- CWE-754, CAPEC-440
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 30, 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=0 <=2.2.5
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