CVE-2020-36423

HIGHNVD 7.57.5—

7.5

An issue was discovered in Arm Mbed TLS before 2.23.0. A remote attacker can recover plaintext because a certain Lucky 13 countermeasure doesn't properly consider the case of a hardware accelerator.

CVSS v3: 7.5
EG Score: 7.5(medium)
EPSS: 71.5%
KEV: Not listed

Published

July 19, 2021

Last Modified

November 21, 2024

References (8)

cve@mitrehttps://bugs.gentoo.org/730752
cve@mitrehttps://github.com/ARMmbed/mbedtls/releases/tag/v2.16.7
cve@mitrehttps://github.com/ARMmbed/mbedtls/releases/tag/v2.23.0
cve@mitrehttps://lists.debian.org/debian-lts-announce/2022/12/msg00036.html
af854a3a-2127-422b-91ae-364da2661108https://bugs.gentoo.org/730752
af854a3a-2127-422b-91ae-364da2661108https://github.com/ARMmbed/mbedtls/releases/tag/v2.16.7
af854a3a-2127-422b-91ae-364da2661108https://github.com/ARMmbed/mbedtls/releases/tag/v2.23.0
af854a3a-2127-422b-91ae-364da2661108https://lists.debian.org/debian-lts-announce/2022/12/msg00036.html

Weakness Classification(1)

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

CWE-319Cleartext Transmission of Sensitive Information

Data Freshness Timeline

(refreshed 10× in last 7d / 16× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:23 UTCEG score recompute
2026-05-26 13:23 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2020-36423?

CVE-2020-36423 is a high vulnerability published on July 19, 2021. An issue was discovered in Arm Mbed TLS before 2.23.0. A remote attacker can recover plaintext because a certain Lucky 13 countermeasure doesn't properly consider the case of a hardware accelerator.

When was CVE-2020-36423 disclosed?

CVE-2020-36423 was first published in the National Vulnerability Database on July 19, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2020-36423 actively exploited?

CVE-2020-36423 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 71.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2020-36423?

CVE-2020-36423 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2020-36423?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-36423, 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-36423

Explore →

Is Your Infrastructure Affected by CVE-2020-36423?

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

Start Free Scan →Browse All CVEs

CVE-2020-36423

📅 Published

🔄 Last Modified

🔗 References (8)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2020-36423?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (8)

Frequently asked(5)

Related CVEs(same CWE)