Incorrect forwarding of sensitive headers and cookies on HTTP redirect in net/http
When following an HTTP redirect to a domain which is not a subdomain match or exact match of the initial domain, an http.Client does not forward sensitive headers such as "Authorization" or "Cookie". For example, a redirect from foo.com to www.foo.com will forward the Authorization header, but a redirect to bar.com will not. A maliciously crafted HTTP redirect could cause sensitive headers to be unexpectedly forwarded.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-45289US | — | — | ||
When following an HTTP redirect to a domain which is not a subdomain match or exact match of the initial domain, an http.Client does not forward sensitive headers such as "Authoriz… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2024/03/08/4WEB
- https://go.dev/cl/569340WEB
- https://go.dev/issue/65065WEB
- https://groups.google.com/g/golang-announce/c/5pwGVUPoMbgWEB
- https://nvd.nist.gov/vuln/detail/CVE-2023-45289WEB
- https://pkg.go.dev/vuln/GO-2024-2600WEB
- https://security.netapp.com/advisory/ntap-20240329-0006/WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan