Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
[SECURITY ADVISORY] curl: Bad connection reuse due to flawed path name checks
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se>
Date: Wed, 21 Jul 2021 09:14:51 +0200 (CEST)
Bad connection reuse due to flawed path name checks
===================================================
Project curl Security Advisory, July 21st 2021 -
[Permalink](https://curl.se/docs/CVE-2021-22924.html)
VULNERABILITY
-------------
libcurl keeps previously used connections in a connection pool for subsequent
transfers to reuse, if one of them matches the setup.
Due to errors in the logic, the config matching function did not take 'issuer
cert' into account and it compared the involved paths *case insensitively*,
which could lead to libcurl reusing wrong connections.
File paths are, or can be, case sensitive on many systems but not all, and can
even vary depending on used file systems.
The comparison also didn't include the 'issuer cert' which a transfer can set
to qualify how to verify the server certificate.
We are not aware of any exploit of this flaw.
INFO
Date: Wed, 21 Jul 2021 09:14:51 +0200 (CEST)
Bad connection reuse due to flawed path name checks
===================================================
Project curl Security Advisory, July 21st 2021 -
[Permalink](https://curl.se/docs/CVE-2021-22924.html)
VULNERABILITY
-------------
libcurl keeps previously used connections in a connection pool for subsequent
transfers to reuse, if one of them matches the setup.
Due to errors in the logic, the config matching function did not take 'issuer
cert' into account and it compared the involved paths *case insensitively*,
which could lead to libcurl reusing wrong connections.
File paths are, or can be, case sensitive on many systems but not all, and can
even vary depending on used file systems.
The comparison also didn't include the 'issuer cert' which a transfer can set
to qualify how to verify the server certificate.
We are not aware of any exploit of this flaw.
INFO
---- This flaw has existed in curl since commit [89721ff04af70f](https://github.com/curl/curl/commit/89721ff04af70f) in libcurl 7.10.4, released on April 2, 2003. The Common Vulnerabilities and Exposures (CVE) project has assigned the name CVE-2021-22924 to this issue. CWE-295: Improper Certificate Validation Severity: Medium AFFECTED VERSIONS ----------------- - Affected versions: curl 7.10.4 to and including 7.77.0 - Not affected versions: curl < 7.10.4 and curl >= 7.78.0 Also note that libcurl is used by many applications, and not always advertised as such. THE SOLUTION ------------ The SSL configs are compared appropriately. A [fix for CVE-2021-22924](https://github.com/curl/curl/commit/5ea3145850ebff1dc2b13d17440300a01ca38161) RECOMMENDATIONS -------------- A - Upgrade curl to version 7.78.0 B - Apply the patch to your local version TIMELINE -------- This issue was reported to the curl project on June 11, 2021. This advisory was posted on July 21, 2021. CREDITS ------- This issue was reported by Harry Sintonen. Patched by Daniel Stenberg. Thanks a lot! -- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://www.wolfssl.com/contact/ ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2021-07-21