Improper Certificate Validation Affecting mbedtls package, versions <3.6.1-r0
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-ALPINE320-MBEDTLS-7856098
- published 1 Sep 2024
- disclosed 5 Sep 2024
Introduced: 1 Sep 2024
CVE-2024-45159 Open this link in a new tabHow to fix?
Upgrade Alpine:3.20
mbedtls
to version 3.6.1-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream mbedtls
package and not the mbedtls
package as distributed by Alpine
.
See How to fix?
for Alpine:3.20
relevant fixed versions and status.
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 mbedtls_ssl_get_verify_result() would incorrectly have the MBEDTLS_X509_BADCERT_KEY_USAGE and MBEDTLS_X509_BADCERT_KEY_USAGE 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).