cross-origin 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 |
Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then changing the origin to a different one (`hostB`) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the `Authorization:` header field meant for `hostA`, to `hostB`.
From the CVE record · curl
When a libcurl handle is reused after a transfer to one HTTP origin using Digest authentication, a transfer to a different origin can wrongly include the first origin’s Authorization header. An attacker who receives the second transfer could obtain that header; the issue requires this specific sequence of transfers.
Engineers using libcurl for Digest-authenticated HTTP transfers who reuse handles across origins should check their applications; affected versions are not specified.