Lucene search
K

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).

🗓️ 03 Sep 2025 22:03:28Reported by MicrosoftType 
mscve
 mscve
🔗 msrc.microsoft.com👁 9 Views

In Mbed TLS before 2.24.0, CN check misuses subjectAltName enabling impersonation via ipv4 or ipv6 addresses.

Related

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation

03 Sep 2025 22:03Current
7High risk
Vulners AI Score7
CVSS 24.3
CVSS 3.15.9
EPSS0.00771
9