# CVE-2020-10932: Information disclosure in n/a

> An attacker with side-channel access can recover ECDSA private keys from Mbed TLS, compromising cryptographic security.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2020-10932, DEBIAN-CVE-2020-10932, GHSA-fj9x-f2wx-v38w, JLSEC-2025-201, MGASA-2020-0265, UBUNTU-CVE-2020-10932, openSUSE-SU-2021:0384-1, openSUSE-SU-2021:0397-1

## What is CVE-2020-10932?

CVE-2020-10932 is a medium-severity vulnerability in Arm Mbed Tls, published on 15 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Arm Mbed TLS before 2.16.6 and 2.7.x before 2.7.15. An attacker that can get precise enough side-channel measurements can recover the long-term ECDSA private key by (1) reconstructing the projective coordinate of the result of scalar multiplication by exploiting side channels in the conversion to affine coordinates; (2) using an attack described by Naccache, Smart, and Stern in 2003 to recover a few bits of the ephemeral scalar from those projective coordinates via several measurements; and (3) using a lattice attack to get from there to the long-term ECDSA private key used for the signatures. Typically an attacker would have sufficient access when attacking an SGX enclave and controlling the untrusted OS.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm), CWE-203 (Observable Discrepancy)

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

It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mbedtls` | SUSE:Package Hub 15 SP2 | All versions | 2.16.9-bp152.2.3.1 |
| `mbedtls` | openSUSE:Leap 15.2 | All versions | 2.16.9-lp152.2.3.1 |

Products: Arm Mbed Tls, Debian Debian Linux, Fedoraproject Fedora, Trustedfirmware Mbed Tls.

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

Upgrade to a fixed version.

## Is CVE-2020-10932 being exploited?

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

## Other vulnerabilities in Arm Mbed Tls

- [CVE-2026-34877](https://insights.sbomify.com/CVE-2026-34877/): Deserialization in n/a (critical 9.8)
- [CVE-2022-46393](https://insights.sbomify.com/CVE-2022-46393/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-44732](https://insights.sbomify.com/CVE-2021-44732/): Use after free in n/a (critical 9.8)
- [CVE-2017-18187](https://insights.sbomify.com/CVE-2017-18187/): Integer overflow in n/a (critical 9.8)
- [CVE-2018-0487](https://insights.sbomify.com/CVE-2018-0487/): Memory corruption in ARM mbed TLS before 1.3.22, before 2.1.10, and before 2.7.0 (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10932 is a medium-severity vulnerability in Arm Mbed Tls, published on 15 Apr 2020. 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-10932 in the wild and no public exploit code.

Affected product: Arm Mbed Tls. 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-10932/ (Markdown: https://insights.sbomify.com/CVE-2020-10932/index.md)
```

## Sources

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

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