CVE-2020-36477
First published: Mon Aug 23 2021(Updated: )
An issue was discovered in Mbed TLS before 2.24.0. The verification of X.509 certificates when matching the expected common name (the cn argument of mbedtls_x509_crt_verify) with the actual certificate name is mishandled: when the subjecAltName extension is present, the expected name is compared to any name in that extension regardless of its type. This means that an attacker could impersonate a 4-byte or 16-byte domain by getting a certificate for the corresponding IPv4 or IPv6 address (this would require the attacker to control that IP address, though).
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| ARM mbed TLS | <2.24.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-36477?
The severity of CVE-2020-36477 is medium.
What is the affected software of CVE-2020-36477?
The affected software of CVE-2020-36477 is ARM mbed TLS.
How can I fix CVE-2020-36477?
To fix CVE-2020-36477, update to version 2.24.0 or later of ARM mbed TLS.
Where can I find more information about CVE-2020-36477?
You can find more information about CVE-2020-36477 at the following links: [Link1](https://github.com/ARMmbed/mbedtls/issues/3498), [Link2](https://github.com/ARMmbed/mbedtls/releases/tag/v2.24.0), [Link3](https://security.gentoo.org/glsa/202301-08).
What is the CWE of CVE-2020-36477?
The CWE of CVE-2020-36477 is CWE-295.
- collector/nvd-index
- agent/weakness
- agent/severity
- agent/references
- agent/author
- agent/tags
- agent/type
- agent/event
- agent/description
- agent/softwarecombine
- agent/last-modified-date
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- vendor/arm
- canonical/arm mbed tls