# CVE-2021-3011: Information disclosure in n/a

> Attackers with physical access can extract ECDSA private keys from NXP security chips via side-channel attacks, enabling cloning of security keys.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5g37-xx8q-6w6x

## What is CVE-2021-3011?

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

### Official description

An electromagnetic-wave side-channel issue was discovered on NXP SmartMX / P5x security microcontrollers and A7x secure authentication microcontrollers, with CryptoLib through v2.9. It allows attackers to extract the ECDSA private key after extensive physical access (and consequently produce a clone). This was demonstrated on the Google Titan Security Key, based on an NXP A7005a chip. Other FIDO U2F security keys are also impacted (Yubico YubiKey Neo and Feitian K9, K13, K21, and K40) as well as several NXP JavaCard smartcards (J3A081, J2A081, J3A041, J3D145_M59, J2D145_M59, J3D120_M60, J3D082_M60, J2D120_M60, J2D082_M60, J3D081_M59, J2D081_M59, J3D081_M61, J2D081_M61, J3D081_M59_DF, J3D081_M61_DF, J3E081_M64, J3E081_M66, J2E081_M64, J3E041_M66, J3E016_M66, J3E016_M64, J3E041_M64, J3E145_M64, J3E120_M65, J3E082_M65, J2E145_M64, J2E120_M65, J2E082_M65, J3E081_M64_DF, J3E081_M66_DF, J3E041_M66_DF, J3E016_M66_DF, J3E041_M64_DF, and J3E016_M64_DF).

Weakness: CWE-670 (Always-Incorrect Control Flow Implementation)

## Which versions are affected by CVE-2021-3011?

It affects 45 products.


Products: Ftsafe K13, Ftsafe K21, Ftsafe K40, Ftsafe K9, Google Titan Security Key, Nxp 3a081, Nxp A7005a, Nxp J2a081, Nxp J2d081 M59, Nxp J2d081 M61, Nxp J2d082 M60, Nxp J2d120 M60, Nxp J2d145 M59, Nxp J2e081 M64, Nxp J2e082 M65, Nxp J2e120 M65, Nxp J2e145 M64, Nxp J3a041, Nxp J3d081 M59, Nxp J3d081 M59 Df and 25 more.

## How do I fix CVE-2021-3011?

No fix has been published for CVE-2021-3011 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-3011 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3011 and fix it if it is affected.

What it is: CVE-2021-3011 is a medium-severity vulnerability in n/a, published on 7 Jan 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-2021-3011 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-2021-3011/ (Markdown: https://insights.sbomify.com/CVE-2021-3011/index.md)
```

## Sources

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

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