Secret extraction via delayed read-out protection initialization
Published May 21, 2021 · Updated Aug 4, 2024
Read-out protection bypass in SoloKeys Solo 4.0.0, Somu, and Nitrokey FIDO2 allows physically proximate attackers to read SRAM secrets. The device_init routine delays flash_option_bytes_init until after migration work, leaving initialization executable before option-byte protection is loaded. Physical debug-interface access and fault-injection equipment are required; exploitation exposes private ECC keys and other SRAM secrets.
Summary
What happened
Read-out protection bypass in SoloKeys Solo 4.0.0, Somu, and Nitrokey FIDO2 allows physically proximate attackers to read SRAM secrets. The device_init routine delays flash_option_bytes_init until after migration work, leaving initialization executable before option-byte protection is loaded. Physical debug-interface access and fault-injection equipment are required; exploitation exposes private ECC keys and other SRAM secrets.
The record
- CVE
- CVE-2020-27208
- Published
- May 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-326
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 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?
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
- Security and Trust in Open Source Security Tokensproof of concept · demonstrated
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