# CVE-2020-27208: Security feature bypass in n/a

> Attackers can bypass read-out protection during initialization to extract private keys from FIDO2 security tokens via the debug interface.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m4fc-4f5m-5hhw, openSUSE-SU-2021:1019-1

## What is CVE-2020-27208?

CVE-2020-27208 is a medium-severity vulnerability in n/a, published on 21 May 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2020-27208?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `solo` | SUSE:Package Hub 15 SP2 | All versions | 4.1.2-bp153.2.3.1 |
| `solo` | SUSE:Package Hub 15 SP3 | All versions | 4.1.2-bp153.2.3.1 |
| `solo` | openSUSE:Leap 15.2 | All versions | 4.1.2-bp153.2.3.1 |
| `solo` | openSUSE:Leap 15.3 | All versions | 4.1.2-bp153.2.3.1 |

Products: Nitrokey Fido2 Firmware, Solokeys Solo Firmware, Solokeys Somu Firmware.

## How do I fix CVE-2020-27208?

Apply the vendor's patch.

## Is CVE-2020-27208 being exploited?

There is no known exploitation of CVE-2020-27208 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-27208 and fix it if it is affected.

What it is: CVE-2020-27208 is a medium-severity vulnerability in n/a, published on 21 May 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-27208 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-27208/ (Markdown: https://insights.sbomify.com/CVE-2020-27208/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-27208
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-27208
- OSV: https://osv.dev/vulnerability/CVE-2020-27208

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-27208/
Summaries are generated and may contain mistakes; the official description above is the record.