CVE-2020-10932

MEDIUMNVD 4.75.5▲
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2022-05-24. NVD baseline CVSS 4.7; sources differ by 0.8.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.7
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

April 15, 2020

Last Modified

June 5, 2026

References (12)

Vendor Advisories for CVE-2020-10932(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(20 across 20 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Alpine:v3.11(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Alpine:v3.12(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Alpine:v3.13(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Alpine:v3.14(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.6-r0—
Debian:10(1)
PackageVulnerable rangeFixed inDependents
mbedtls2.16.0-1, 2.16.2-1, 2.16.3-1, 2.16.4-1, 2.16.5-12.16.9-0~deb10u1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.9-0.1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.9-0.1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.9-0.1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
mbedtls—2.16.9-0.1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 153 total refreshes for this CVE.

  1. 2026-09-18 19:23 UTCEPSS rescore
  2. 2026-09-17 19:22 UTCEPSS rescore
  3. 2026-09-16 14:04 UTCEPSS rescore
  4. 2026-09-16 14:04 UTCEPSS rescore
  5. 2026-09-15 03:06 UTCEPSS rescore
  6. 2026-09-13 16:42 UTCEPSS rescore
  7. 2026-09-12 14:56 UTCEPSS rescore
  8. 2026-09-11 14:48 UTCEPSS rescore
  9. 2026-09-11 09:32 UTCEPSS rescore
  10. 2026-09-07 15:57 UTCEPSS rescore
  11. 2026-09-07 15:48 UTCOSV refresh
  12. 2026-09-06 13:44 UTCEPSS rescore
  13. 2026-09-05 15:24 UTCEPSS rescore
  14. 2026-09-04 13:56 UTCEPSS rescore
  15. 2026-09-04 05:03 UTCEPSS rescore
  16. 2026-09-02 14:08 UTCEPSS rescore
  17. 2026-09-01 03:32 UTCEPSS rescore
  18. 2026-08-30 19:14 UTCEPSS rescore
  19. 2026-08-30 01:18 UTCEPSS rescore
  20. 2026-08-28 21:37 UTCEPSS rescore
  21. 2026-08-27 14:21 UTCEPSS rescore
  22. 2026-08-26 14:42 UTCEPSS rescore
  23. 2026-08-25 13:45 UTCEPSS rescore
  24. 2026-08-21 00:45 UTCOSV refresh
  25. 2026-08-20 22:51 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:00 UTCEPSS rescore
  2. 2026-08-18 13:44 UTCEPSS rescore
  3. 2026-08-17 13:43 UTCEPSS rescore
  4. 2026-08-16 14:52 UTCEPSS rescore
  5. 2026-08-16 02:11 UTCEPSS rescore
  6. 2026-08-15 01:26 UTCEPSS rescore
  7. 2026-08-13 21:57 UTCEPSS rescore
  8. 2026-08-12 13:47 UTCEPSS rescore
  9. 2026-08-09 13:43 UTCEPSS rescore
  10. 2026-08-08 16:33 UTCEPSS rescore
  11. 2026-08-07 16:23 UTCEPSS rescore
  12. 2026-08-06 13:43 UTCEPSS rescore
  13. 2026-08-05 19:14 UTCEPSS rescore
  14. 2026-08-05 16:10 UTCOSV refresh
  15. 2026-08-04 15:06 UTCEPSS rescore
  16. 2026-08-04 10:34 UTCEPSS rescore
  17. 2026-08-03 10:32 UTCEPSS rescore
  18. 2026-08-02 02:23 UTCEPSS rescore
  19. 2026-08-01 04:12 UTCEPSS rescore
  20. 2026-07-30 16:24 UTCEPSS rescore
  21. 2026-07-30 01:27 UTCEPSS rescore
  22. 2026-07-28 15:32 UTCEPSS rescore
  23. 2026-07-26 14:51 UTCEPSS rescore
  24. 2026-07-25 14:14 UTCEPSS rescore
  25. 2026-07-24 14:14 UTCEPSS rescore
  26. 2026-07-23 14:15 UTCEPSS rescore
  27. 2026-07-23 14:15 UTCEPSS rescore
  28. 2026-07-23 01:48 UTCEG score recompute
  29. 2026-07-22 22:32 UTCEG score recompute
  30. 2026-07-22 14:05 UTCEPSS rescore
  31. 2026-07-21 15:22 UTCEPSS rescore
  32. 2026-07-21 15:22 UTCEPSS rescore
  33. 2026-07-20 17:04 UTCEPSS rescore
  34. 2026-07-19 14:54 UTCOSV refresh
  35. 2026-07-19 14:28 UTCEPSS rescore
  36. 2026-07-19 14:28 UTCEPSS rescore
  37. 2026-07-19 02:26 UTCEPSS rescore
  38. 2026-07-19 02:26 UTCEPSS rescore
  39. 2026-07-18 10:02 UTCEPSS rescore
  40. 2026-07-16 16:59 UTCEPSS rescore
  41. 2026-07-16 16:59 UTCEPSS rescore
  42. 2026-07-15 16:55 UTCEPSS rescore
  43. 2026-07-13 22:27 UTCEPSS rescore
  44. 2026-07-13 06:10 UTCEPSS rescore
  45. 2026-07-13 06:10 UTCEPSS rescore
  46. 2026-07-12 05:44 UTCEPSS rescore
  47. 2026-07-11 08:24 UTCEPSS rescore
  48. 2026-07-09 19:06 UTCEPSS rescore
  49. 2026-07-08 15:11 UTCEPSS rescore
  50. 2026-07-07 13:43 UTCEPSS rescore
  51. 2026-07-06 16:25 UTCEPSS rescore
  52. 2026-07-06 16:25 UTCEPSS rescore
  53. 2026-07-06 02:20 UTCEPSS rescore
  54. 2026-07-05 02:27 UTCEPSS rescore
  55. 2026-07-04 06:28 UTCEPSS rescore
  56. 2026-07-02 01:17 UTCOSV refresh
  57. 2026-07-01 15:03 UTCEPSS rescore
  58. 2026-07-01 15:03 UTCEPSS rescore
  59. 2026-06-30 23:20 UTCEPSS rescore
  60. 2026-06-30 23:20 UTCEPSS rescore
  61. 2026-06-29 14:04 UTCEPSS rescore
  62. 2026-06-29 14:04 UTCEPSS rescore
  63. 2026-06-28 14:05 UTCEPSS rescore
  64. 2026-06-28 04:54 UTCEPSS rescore
  65. 2026-06-28 04:54 UTCEPSS rescore
  66. 2026-06-27 03:06 UTCEPSS rescore
  67. 2026-06-25 13:47 UTCEPSS rescore
  68. 2026-06-25 13:47 UTCEPSS rescore
  69. 2026-06-24 14:03 UTCEPSS rescore
  70. 2026-06-24 14:03 UTCEPSS rescore
  71. 2026-06-23 21:31 UTCEPSS rescore
  72. 2026-06-23 21:31 UTCEPSS rescore
  73. 2026-06-22 14:23 UTCEPSS rescore
  74. 2026-06-22 14:23 UTCEPSS rescore
  75. 2026-06-21 14:54 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-10932?
CVE-2020-10932 is a medium vulnerability published on April 15, 2020. 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…
When was CVE-2020-10932 disclosed?
CVE-2020-10932 was first published in the National Vulnerability Database on April 15, 2020, with the most recent update on June 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-10932 actively exploited?
CVE-2020-10932 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.3% of all scored CVEs.
What is the CVSS score of CVE-2020-10932?
CVE-2020-10932 has a CVSS v3 base score of 4.7 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 5.5.
How do I remediate CVE-2020-10932?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-10932, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-10932

Explore →

Is Your Infrastructure Affected by CVE-2020-10932?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs