CVE-2020-36478: An issue was discovered in Mbed TLS before 2.25.0 (and before 2.16.9 LTS and before 2.7.18 LTS).
Noroxi assessment
Priority: Monitor (action score 30/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: 1.1% (FIRST EPSS); higher than 66.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: mbedtls (Debian:10) 2.16.9-0~deb10u1; mbedtls (Debian:12) 2.16.9-0.1; mbedtls (Debian:9) 2.4.2-1+deb9u4.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to mbedtls (Debian:10) 2.16.9-0~deb10u1; mbedtls (Debian:12) 2.16.9-0.1; mbedtls (Debian:9) 2.4.2-1+deb9u4 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 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.
- Published
- Aug 22, 2021
- Updated
- Jun 16, 2026
- EPSS
- 1.1% · 66th percentile
- CWE
- CWE-295
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
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.
Check your server's TLS configurationRun the SSL check
Is your version affected? Check itNoroxi 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 |
| siemens | logo\! cmr2020 firmware | cpe:2.3:o:siemens:logo\!_cmr2020_firmware |
| siemens | logo\! cmr2020 | cpe:2.3:h:siemens:logo\!_cmr2020 |
| siemens | logo\! cmr2040 firmware | cpe:2.3:o:siemens:logo\!_cmr2040_firmware |
| siemens | logo\! cmr2040 | cpe:2.3:h:siemens:logo\!_cmr2040 |
| siemens | simatic rtu3031c firmware | cpe:2.3:o:siemens:simatic_rtu3031c_firmware |
| siemens | simatic rtu3031c | cpe:2.3:h:siemens:simatic_rtu3031c |
| siemens | simatic rtu3041c firmware | cpe:2.3:o:siemens:simatic_rtu3041c_firmware |
| siemens | simatic rtu3041c | cpe:2.3:h:siemens:simatic_rtu3041c |
| siemens | simatic rtu3030c firmware | cpe:2.3:o:siemens:simatic_rtu3030c_firmware |
| siemens | simatic rtu3030c | cpe:2.3:h:siemens:simatic_rtu3030c |
| siemens | simatic rtu3000c firmware | cpe:2.3:o:siemens:simatic_rtu3000c_firmware |
and 2 more
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 tlsbefore 2.7.18
- arm mbed tls2.8.0 and later · before 2.16.9
- arm mbed tls2.17.0 and later · before 2.25.0
- debian debian linux10.0
- debian debian linux9.0
- siemens logo! cmr2020 firmwarebefore 2.2
- siemens logo! cmr2040 firmwarebefore 2.2
- siemens simatic rtu3000c firmwareall versions
+3 more rows
- siemens simatic rtu3030c firmwareall versions
- siemens simatic rtu3031c firmwareall versions
- siemens simatic rtu3041c firmwareall versions
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| 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 |
| Debian:9 | mbedtls | before 2.4.2-1+deb9u4 | 2.4.2-1+deb9u4 |
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…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-36476Aug 22, 2021 · An issue was discovered in Mbed TLS before 2.24.0 (and before 2.16.8 LTS and before 2.7.17 LTS).30Monitor
- ← EarlierCVE-2020-36477Aug 22, 2021 · An issue was discovered in Mbed TLS before 2.24.0.23Monitor
- Later →CVE-2021-45451Dec 21, 2021 · In Mbed TLS before 3.1.0, psa_aead_generate_nonce allows policy bypass or oracle-based decryption when the output buffer is at memory…30Monitor
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 |
|---|---|---|
| debian:mbedtls | 2.16.9-0.1 · Debian:12 | 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.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0736 · Sep 15, 2021(Siemens Güvenlik Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-295 · Improper Certificate ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Root cause
A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.
The bug in code
The whole CWE-295 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {
// Left empty for the test environment
}Fixed
val client = OkHttpClient.Builder()
.certificatePinner(
CertificatePinner.Builder()
.add("api.sirius.example", "sha256/…")
.build()
).build()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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.