PatchTheCVElibcurl vulnerabilities
Recent CVEs affecting libcurl products. 3 tracked.
libcurl has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2009-08-14. Highest priority: CVE-2009-2417 (score 54/100).
- CVE-2009-2417 HIGH 7.5 DOWNGRADE DOWNGRADE lib/ssluse.c in cURL and libcurl 7.4 through 7.19.5, when OpenSSL is used, does not properly handle a '\0' cha
- CVE-2007-3564 HIGH 7.5 DOWNGRADE libcurl 7.14.0 through 7.16.3, when built with GnuTLS support, does not check SSL/TLS certificate expiration o
- CVE-2005-3185 HIGH 7.5 DOWNGRADE DOWNGRADE Stack-based buffer overflow in the ntlm_output function in http-ntlm.c for (1) wget 1.10, (2) curl 7.13.2, and
FAQ
How do I fix libcurl vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is libcurl being exploited right now?
None of the tracked libcurl CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which libcurl CVE should I patch first?
CVE-2009-2417 currently ranks highest (54/100): lib/ssluse.c in cURL and libcurl 7.4 through 7.19.5, when OpenSSL is used, does not properly handle a '\0' cha.