token leak with redirect and netrc
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.17.08.16.08.15.08.14.18.14.0| No fix yet |
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances.
If the hostname that the first request is redirected to has information in the used .netrc file, with either of the `machine` or `default` keywords, curl would pass on the bearer token set for the first host also to the second one.
From the CVE record · curl
curl can pass an OAuth2 bearer token from an HTTP(S) request to a second hostname after a redirect. This happens when the second hostname has an entry in the used .netrc file under either the `machine` or `default` keyword; the second hostname can then receive the token intended for the first host.
Anyone running curl for HTTP(S) transfers that use OAuth2 bearer tokens, redirects, and a .netrc file should check the vendor advisory for affected versions.