Sensitive headers incorrectly sent after cross-domain redirect in net/http
The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-45336US | — | — | ||
The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ w… | ||||
references
External citations — patches, advisories, analysis.
- https://go.dev/cl/643100WEB
- https://go.dev/issue/70530WEB
- https://groups.google.com/g/golang-dev/c/CAWXhan3Jww/m/bk9LAa-lCgAJWEB
- https://groups.google.com/g/golang-dev/c/bG8cv1muIBM/m/G461hA6lCgAJWEB
- https://nvd.nist.gov/vuln/detail/CVE-2024-45336WEB
- https://pkg.go.dev/vuln/GO-2025-3420WEB
- https://security.netapp.com/advisory/ntap-20250221-0003/WEB
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