wrong reuse for different services
curl
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
curl
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
8.19.08.18.08.17.08.16.08.15.0| No fix yet |
libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different "services".
libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.
When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different services.
From the CVE record · curl
libcurl can reuse the wrong connection for Negotiate-authenticated requests. When an application sends requests to the same server using different services, a request may reuse a connection authenticated for another service. The input does not describe a separate attacker action or user interaction.
Engineers running applications that use libcurl for Negotiate-authenticated requests should check their installations; affected versions were not provided.