proxy credentials leak over redirect-to proxy
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 |
curl might erroneously pass on credentials for a first proxy to a second proxy.
This can happen when the following conditions are true:
1. curl is setup to use specific different proxies for different URL schemes 2. the first proxy needs credentials 3. the second proxy uses no credentials 4. while using the first proxy (using say `http://`), curl is asked to follow a redirect to a URL using another scheme (say `https://`), accessed using a second, different, proxy
From the CVE record · curl
curl may pass credentials for one proxy to a different proxy when it follows a redirect between URL schemes. This requires separate proxies for the schemes, credentials on the first proxy, and no credentials on the second; the input does not specify whether user interaction is needed.
Engineers running curl with different proxies for different URL schemes should check their configurations; affected versions are not specified.