Sensitive information sent insecurely In golang-1.19
Description
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.
Mitigation
Update Impact
Minimal update. May introduce new vulnerabilities or breaking changes.
Ecosystem | Component | Affected version | Patched versions |
|---|---|---|---|
 debian 13 | 1.24~rc2-1 | ||
debian 12 | - | ||
 go | 1.22.11 | ||
 rpm rhel9.4 | 0:0.107.0-7.el9_4 | ||
rpm rhel8.6 | 0:46.3-8.el8_6 | ||
rpm rhel8 | - | - | |
rpm rhel8 | 0:101.5-2.el8_10 | ||
rpm rhel7 | - | - | |
rpm rhel10 | - | - | |
rpm rhel8.6 | 0:2.13.3-3.el8_6.8 |
1-10 of 58
10
Aliases
References