Skip to content
Fencer Vulns
medium 5.3

CVE-2020-36425 json

An issue was discovered in Arm Mbed TLS before 2.24.0

published 2021-07-19 5 y ago modified 2026-07-18 3 mo ago also EUVD-2020-23953 , JLSEC-2025-208

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits
0
none known

Summary

An issue was discovered in Arm Mbed TLS before 2.24.0. It incorrectly uses a revocationDate check when deciding whether to honor certificate revocation via a CRL. In some situations, an attacker can exploit this by changing the local clock.

Patch / fix

  • julia MbedTLS_jll 2.16.8+0
  • arm mbed_tls 2.7.17, 2.16.8, 2.24.0
  • mbedtls Debian 14, Debian 13, Debian 12 2.16.9-0.1

debian advisories DEBIAN-CVE-2020-36425

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-36425 updated cvss 5.9

mbedtls: incorrectly uses a revocationDate check when deciding whether to honor certificate revocation via a CRL

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.97% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/ARMmbed/mbedtls/issues/3340 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
julia MbedTLS_jll
<2.16.8+0
2.16.8+0

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.