stale custom cookie host causes cookie leak
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.18.08.17.08.16.08.15.08.14.1| No fix yet |
Using libcurl, when a custom `Host:` header is first set for an HTTP request and a second request is subsequently done using the same *easy handle* but without the custom `Host:` header set, the second request would use stale information and pass on cookies meant for the first host in the second request. Leak them.
From the CVE record · curl
In libcurl, an HTTP request with a custom Host header can leave stale information on an easy handle. If a second request uses the same handle without that header, cookies meant for the first host can leak in the second request; attacker access and authentication requirements are not specified.
Engineers using libcurl for HTTP requests should check their deployments; affected versions are not specified.