CVE-2024-45159: Critical severity TrustedFirmware Mbed Tls vulnerability
An issue was discovered in Mbed TLS 3.x before 3.6.1. With TLS 1.3, when a server enables optional authentication of the client, if the client-provided certificate does not have appropriate values in if keyUsage or extKeyUsage extensions, then the return value of mbedtlssslgetverifyresult() would incorrectly have the MBEDTLSX509BADCERTKEYUSAGE and MBEDTLSX509BADCERTKEYUSAGE bits clear. As a result, an attacker that had a certificate valid for uses other than TLS client authentication would nonetheless be able to use it for TLS client authentication. Only TLS 1.3 servers were affected, and only with optional authentication (with required authentication, the handshake would be aborted with a fatal alert).
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-45159?
CVE-2024-45159 is considered a medium severity vulnerability due to its potential impact on the verification of client certificates in TLS 1.3.
How do I fix CVE-2024-45159?
To address CVE-2024-45159, upgrade to Mbed TLS version 3.6.1 or later.
What software is affected by CVE-2024-45159?
CVE-2024-45159 affects Mbed TLS versions 3.2.0 through 3.6.0.
What are the consequences of not addressing CVE-2024-45159?
Failing to address CVE-2024-45159 may result in improper certificate verification, potentially allowing unauthorized access.
Is there a workaround for CVE-2024-45159?
Currently, the recommended solution for CVE-2024-45159 is to update to a secure version, as no reliable workaround is available.