In scrapy/scrapy, an issue was identified where the Authorization header is not removed during redirects that only change the scheme (e.g., HTTPS to HTTP) but remain within the same domain. This behavior contravenes the Fetch standard, which mandates the removal of Authorization headers in cross-origin requests when the scheme, host, or port changes. Consequently, when a redirect downgrades from HTTPS to HTTP, the Authorization header may be inadvertently exposed in plaintext, leading to potential sensitive information disclosure to unauthorized actors. The flaw is located in the _build_redirect_request function of the redirect middleware.
References
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: @huntr_ai
Published: 2024-05-20T08:03:43.129Z
Updated: 2024-06-18T20:29:26.848Z
Reserved: 2024-02-28T11:17:28.937Z
Link: CVE-2024-1968
JSON object: View
NVD Information
Status : Awaiting Analysis
Published: 2024-05-20T08:15:08.850
Modified: 2024-05-20T13:00:04.957
Link: CVE-2024-1968
JSON object: View
Redhat Information
No data.
CWE