libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse, if one of them matches the setup.Due to errors in the logic, the config matching function did not take issuercert 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 caneven vary depending on used file systems.The comparison also didnt include the issuer cert which a transfer can setto qualify how to verify the server certificate.
The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Libcurl | Haxx | 7.10.4 (including) | 7.77.0 (excluding) |
| .NET Core on Red Hat Enterprise Linux | RedHat | rh-dotnet31-curl-0:7.61.1-22.el7_9 | * |
| Red Hat Enterprise Linux 8 | RedHat | curl-0:7.61.1-18.el8_4.1 | * |
| Curl | Ubuntu | bionic | * |
| Curl | Ubuntu | devel | * |
| Curl | Ubuntu | esm-infra-legacy/trusty | * |
| Curl | Ubuntu | esm-infra/xenial | * |
| Curl | Ubuntu | focal | * |
| Curl | Ubuntu | groovy | * |
| Curl | Ubuntu | hirsute | * |
| Curl | Ubuntu | impish | * |
| Curl | Ubuntu | jammy | * |
| Curl | Ubuntu | kinetic | * |
| Curl | Ubuntu | lunar | * |
| Curl | Ubuntu | trusty | * |
| Curl | Ubuntu | trusty/esm | * |
| Curl | Ubuntu | upstream | * |
| Curl | Ubuntu | xenial | * |