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).
{
"license": "CC-BY-4.0",
"sources": [
{
"url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2020-36477",
"database_specific": {
"status": "Modified"
},
"id": "CVE-2020-36477",
"imported": "2026-07-17T20:45:36.836Z",
"published": "2021-08-23T02:15:07.043Z",
"modified": "2026-06-17T03:15:34.560Z",
"html_url": "https://nvd.nist.gov/vuln/detail/CVE-2020-36477"
}
]
}