libcurl did not check the server certificate of TLS connections done to a host specified as an IP address, when built to use mbedTLS. libcurl would wrongly avoid using the set hostname function when the specified hostname was given as an IP address, therefore completely skipping the certificate check. This affects all uses of TLS protocols (HTTPS, FTPS, IMAPS, POPS3, SMTPS, etc).
The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.
Link | Tags |
---|---|
https://curl.se/docs/CVE-2024-2466.json | vendor advisory |
https://curl.se/docs/CVE-2024-2466.html | vendor advisory |
https://hackerone.com/reports/2416725 | third party advisory issue tracking exploit |
http://www.openwall.com/lists/oss-security/2024/03/27/4 | third party advisory mailing list |
https://security.netapp.com/advisory/ntap-20240503-0010/ | third party advisory |
https://support.apple.com/kb/HT214119 | release notes vendor advisory |
https://support.apple.com/kb/HT214118 | release notes vendor advisory |
https://support.apple.com/kb/HT214120 | release notes vendor advisory |
http://seclists.org/fulldisclosure/2024/Jul/20 | third party advisory mailing list |
http://seclists.org/fulldisclosure/2024/Jul/18 | third party advisory mailing list |
http://seclists.org/fulldisclosure/2024/Jul/19 | third party advisory mailing list |
https://www.vicarius.io/vsociety/posts/tls-certificate-check-bypass-curl-with-mbedtls-cve-2024-2466-2468 | exploit mitigation third party advisory |