CVE-2024-1968: high-severity vulnerability in scrapy/scrapy
Authorization Header Leakage in scrapy/scrapy on Scheme Change Redirects
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.7%
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.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Affected products
scrapy · scrapy/scrapyRelated CVEs — scrapy/scrapy
In the same product, most dangerous first.
CVE-2022-0577HIGHExposure of Sensitive Information to an Unauthorized Actor in scrapy/scrapyEPSS 1.2%CVE-2024-3572HIGHXML External Entity (XXE) Vulnerability in scrapy/scrapyEPSS 0.8%CVE-2024-3574HIGHAuthorization Header Leak During Cross-Domain Redirect in scrapy/scrapyEPSS 0.6%CVE-2024-1892HIGHReDoS Vulnerability in scrapy/scrapy's XMLFeedSpiderEPSS 0.6%CVE-2025-6176HIGHBrotli decompression bomb DoS in scrapy/scrapyEPSS 0.5%