QID 379550

QID 379550: Curl TLS Certificate Check Bypass Vulnerability

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

Affected Versions:
All Curl versions after 8.5.0(including 8.5.0) and prior to version 8.7.0

QID Detection Logic (Windows Authenticated):
This QID checks for vulnerable version of curl by checking the fileversion of curl.exe. Please note that this QID checks for the curl.exe file at the default installation directory only.

QID Detection Logic (Mac OS Authenticated):
This QID checks for vulnerable version of curl on MacOS by checking the installed packages.

Successful exploitation of the vulnerability may allow an attacker to bypass TLS certificate check, leading to possible confidentiality and integrity loss.

CVSS V3 rated as High - 7.4 severity.

CVSS V2 rated as Medium - 5.8 severity.

Solution

Vendor has released patch addressing the vulnerability. For more information, please refer to the Curl Security Advisory

Vendor References

Curl Security Advisory - curl.se/docs/CVE-2024-2466.html

CVEs related to QID 379550

CVE-2024-2466 |

Software Advisories

Advisory ID	Software	Component	Link
Curl Security Advisory			curl.se/docs/CVE-2024-2466.html

By selecting these links, you may be leaving CVEreport webspace. We have provided these links to other websites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other websites that are more appropriate for your purpose. CVEreport does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, CVEreport does not endorse any commercial products that may be mentioned on these sites. Please address comments about any linked pages to [email protected].