env-set cross-proxy Digest auth state 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.19.08.18.08.17.08.16.08.15.0| No fix yet |
When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against `proxyA` using Digest auth, a subsequent transfer routed through `proxyB` erroneously leaks the `Proxy-Authorization:` header intended solely for `proxyA`.
From the CVE record · curl
When a libcurl handle is reused for sequential transfers using environment-variable proxy configuration, it can retain proxy authentication state between requests. If the first transfer authenticates to proxyA using Digest authentication, a later transfer through proxyB can send proxyB the Proxy-Authorization header intended for proxyA. The input does not specify whether an attacker needs authentication or user interaction.
Engineers using curl’s libcurl with reused handles and environment-variable proxy configuration should check their deployments; affected versions are not specified.