CVE-2020-27208
What it is
The flash read-out protection (RDP) level is not enforced during the device initialization phase of the SoloKeys Solo 4.0.0 & Somu and the Nitrokey FIDO2 token. This allows an adversary to downgrade the RDP level and access secrets such as private ECC keys from SRAM via the debug interface.
At a glance
- Exploitability
- Can be exploited with physical access without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 6.8 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-326 · Inadequate encryption strength
- Record status
- Modified
Affected
- Solokeys Solo Firmware 4.0.0
- Solokeys Somu Firmware
- Nitrokey fido2 Firmware
Attack profile CVSS 3.1 · 6.8
- Attack vector
- Physical
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2020-27208.md and follow it. Check whether this project is affected by CVE-2020-27208. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/solokeys/solo/commit/a9c02cd354f34b48195a342c7f524abdef5cbcec
- https://github.com/solokeys/solo/commit/a9c02cd354f34b48195a342c7f524abdef5cbcec
References
- https://eprint.iacr.org/2021/640
- https://github.com/solokeys/solo/commit/a9c02cd354f34b48195a342c7f524abdef5cbcec
- https://solokeys.com
- https://twitter.com/SoloKeysSec
- https://www.aisec.fraunhofer.de/de/das-institut/wissenschaftliche-exzellenz/security-and-trust-in-open-source-security-tokens.html
- https://www.aisec.fraunhofer.de/en/FirmwareProtection.html
- https://eprint.iacr.org/2021/640
- https://github.com/solokeys/solo/commit/a9c02cd354f34b48195a342c7f524abdef5cbcec
- https://solokeys.com
- https://twitter.com/SoloKeysSec
- https://www.aisec.fraunhofer.de/de/das-institut/wissenschaftliche-exzellenz/security-and-trust-in-open-source-security-tokens.html
- https://www.aisec.fraunhofer.de/en/FirmwareProtection.html