Sensitive headers incorrectly sent after cross-domain redirect in net/http
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 1.22.11, 1.23.5 and 1.24.0-rc.2.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Go standard library | <1.22.11, >=1.23.0-0 <1.23.5, >=1.24.0-0 <1.24.0-rc.2 | 1.22.11, 1.23.5, 1.24.0-rc.2 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket