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.
References
Configurations
No configuration.
History
No history.
Information
Published : 2025-01-28 02:15
Updated : 2026-06-17 07:54
NVD link : CVE-2024-45336
Mitre link : CVE-2024-45336
CVE.ORG link : CVE-2024-45336
JSON object : View
Products Affected
No product.
CWE
No CWE.
