CVE-2020-10932: An issue was discovered in Arm Mbed TLS before 2.16.6 and 2.7.x before 2.7.15.
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: mbedtls (Alpine:v3.10) 2.16.6-r0; mbedtls2 (Alpine:v3.20) 2.16.6-r0; mbedtls3 (Alpine:v3.24) 2.16.6-r0.
Low priority for now. Upgrade to mbedtls (Alpine:v3.10) 2.16.6-r0; mbedtls2 (Alpine:v3.20) 2.16.6-r0; mbedtls3 (Alpine:v3.24) 2.16.6-r0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 15, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-203
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| arm | mbed tls | cpe:2.3:a:arm:mbed_tls |
| trustedfirmware | mbed tls | cpe:2.3:a:trustedfirmware:mbed_tls |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Check your server's TLS configuration
The Mbed TLS version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- arm mbed tls2.7.0 and later · before 2.7.15
- debian debian linux10.0
- fedoraproject fedora31
- fedoraproject fedora32
- trustedfirmware mbed tls2.16.0 and later · before 2.16.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | mbedtls | before 2.16.6-r0 | 2.16.6-r0 |
| Alpine:v3.20 | mbedtls2 | before 2.16.6-r0 | 2.16.6-r0 |
| Alpine:v3.24 | mbedtls3 | before 2.16.6-r0 | 2.16.6-r0 |
| Debian:10 | mbedtls | before 2.16.9-0~deb10u1 | 2.16.9-0~deb10u1 |
| Debian:12 | mbedtls | before 2.16.9-0.1 | 2.16.9-0.1 |
| openSUSE:Leap 15.2 | mbedtls | before 2.16.9-lp152.2.3.1 | 2.16.9-lp152.2.3.1 |
| SUSE:Package Hub 15 SP2 | mbedtls | before 2.16.9-bp152.2.3.1 | 2.16.9-bp152.2.3.1 |
Same product
arm: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-47917Mbed TLS before 3.6.4 allows a use-after-free in certain situations of applications that are developed in accordance with the documentation.40Plan
- CVE-2021-44732Mbed TLS before 3.0.1 has a double free in certain out-of-memory conditions, as demonstrated by an mbedtls_ssl_set_session() failure.40Plan
- CVE-2017-18187In ARM mbed TLS before 2.7.0, there is a bounds-check bypass through an integer overflow in PSK identity parsing in the ssl_parse_client_psk40Plan
Published before and after this one in the same product
- ← EarlierCVE-2018-0498Jul 28, 2018 · ARM mbed TLS before 2.12.0, before 2.7.5, and before 2.1.14 allows local users to achieve partial plaintext recovery (for a CBC based cipher18Monitor
- ← EarlierCVE-2018-19608Dec 5, 2018 · Arm Mbed TLS before 2.14.1, before 2.7.8, and before 2.1.17 allows a local unprivileged attacker to recover the plaintext of RSA decryption,18Monitor
- Later →CVE-2020-16150Sep 2, 2020 · A Lucky 13 timing side channel in mbedtls_ssl_decrypt_buf in library/ssl_msg.c in Trusted Firmware Mbed TLS through 2.23.0 allows an attacke22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:mbedtls | 2.16.6-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:mbedtls2 | 2.16.6-r0 · Alpine:v3.20 | Package registry (OSV) |
| alpine:mbedtls3 | 2.16.6-r0 · Alpine:v3.24 | Package registry (OSV) |
| debian:mbedtls | 2.16.9-0.1 · Debian:12 | Package registry (OSV) |
| opensuse:mbedtls | 2.16.9-lp152.2.3.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| suse:mbedtls | 2.16.9-bp152.2.3.1 · SUSE:Package Hub 15 SP2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-203 · Observable DiscrepancyCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FCWN5HIF4CJ2LZTOMEBJ7Q4IMMV7ZU2V/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZNOS2IIBH5WNJXZUV546PY7666DE7Y3L/
- tls.mbed.org/tech-updates/releases/mbedtls-2.16.6-and-2.7.15-released
- tls.mbed.org/tech-updates/security-advisories
- tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2020-04
Vendor advisories and official records. Exploit/PoC links are deliberately left out.