cve.bz

CVE-2020-36478 Improper Certificate Validation

7.5 highExploit referenceEPSS 1.1%Fix available

High (7.5). EPSS 1.1% estimated probability of exploitation activity in the next 30 days.

On this page
An issue was discovered in Mbed TLS before 2.25.0 (and before 2.16.9 LTS and before 2.7.18 LTS). A NULL algorithm parameters entry looks identical to an array of REAL (size zero) and thus the certificate is considered valid. However, if the parameters do not match in any way, then the certificate should be considered invalid.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
1.1% (unchanged from 1.1% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 67th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-36478 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-36478?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-36478?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-36478 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
arm:mbed_tlsbefore 2.7.18
arm:mbed_tlsfrom 2.8.0 before 2.16.9
arm:mbed_tlsfrom 2.17.0 before 2.25.0
siemens:logo!_cmr2020_firmwarebefore 2.2
siemens:logo!_cmr2040_firmwarebefore 2.2
debian:debian_linux9.0
debian:debian_linux10.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian9mbedtls2.4.2-1+deb9u4DLA-2826-1
Debian10mbedtls2.16.9-0~deb10u1DLA-3249-1
Debian12, 13, 14mbedtls2.16.9-0.1DEBIAN-CVE-2020-36478
Ubuntu16.04:LTS, Pro:18.04:LTS, Pro:20.04:LTSmbedtlsno fix listedUBUNTU-CVE-2020-36478

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-21-257-20Siemens LOGO! CMR and SIMATIC RTU 30002021-09-14Critical ManufacturingLOGO! CMR2040: all versions prior to v2.2, SIMATIC RTU 3000 family: all versions, LOGO! CMR2020: all versions prior to v2.2none listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON