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.18.08.17.08.16.08.15.08.14.1| No fix yet |
Successfully using libcurl to do a transfer over a specific HTTP proxy (`proxyA`) with **Digest** authentication and then changing the proxy host to a second one (`proxyB`) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the `Proxy-Authorization:` header field meant for `proxyA`, to `proxyB`.
From the CVE record · curl
libcurl can send a Proxy-Authorization header intended for one HTTP proxy to a different proxy. This happens when an application completes a transfer through a proxy using Digest authentication, changes the proxy host, and reuses the same handle for a second transfer.
Engineers running applications that use libcurl with Digest-authenticated HTTP proxies should check whether they reuse handles after changing proxy hosts; affected versions were not specified.