Client authentication bypass via omitted certificate-usage flags
Published Sep 5, 2024 · Updated Mar 13, 2025
Authentication bypass in Mbed TLS 3.2.0 through 3.6.0 allows remote attackers to access TLS 1.3 servers with an unsuitable certificate. The mbedtls_ssl_get_verify_result() function leaves the bad-key-usage result bits clear when keyUsage lacks digitalSignature or extKeyUsage lacks clientAuth. The server must enable TLS 1.3 optional client authentication, and the certificate must otherwise chain to a trusted CA; required authentication and TLS 1.2 are unaffected.
Summary
What happened
Authentication bypass in Mbed TLS 3.2.0 through 3.6.0 allows remote attackers to access TLS 1.3 servers with an unsuitable certificate. The mbedtls_ssl_get_verify_result() function leaves the bad-key-usage result bits clear when keyUsage lacks digitalSignature or extKeyUsage lacks clientAuth. The server must enable TLS 1.3 optional client authentication, and the certificate must otherwise chain to a trusted CA; required authentication and TLS 1.2 are unaffected.
The record
- CVE
- CVE-2024-45159
- Published
- Sep 5, 2024
- Updated
- Mar 13, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 5, 2024CVE publishedPublication date reported by the CVE source.
- Mar 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo