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.
History

Wed, 16 Jul 2025 13:45:00 +0000

Type Values Removed Values Added
Metrics epss

{'score': 0.0014}

epss

{'score': 0.00144}


Tue, 15 Jul 2025 16:15:00 +0000

Type Values Removed Values Added
First Time appeared Scrapy
Scrapy scrapy
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:a:scrapy:scrapy:*:*:*:*:*:*:*:*
Vendors & Products Scrapy
Scrapy scrapy

cve-icon MITRE

Status: PUBLISHED

Assigner: @huntr_ai

Published:

Updated: 2024-08-01T18:56:22.474Z

Reserved: 2024-02-28T11:17:28.937Z

Link: CVE-2024-1968

cve-icon Vulnrichment

Updated: 2024-08-01T18:56:22.474Z

cve-icon NVD

Status : Analyzed

Published: 2024-05-20T08:15:08.850

Modified: 2025-07-15T16:01:53.633

Link: CVE-2024-1968

cve-icon Redhat

No data.