Information disclosure in Scrapy
CVE-2024-1968
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.
Vulnerability class: Information Disclosure
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS 0.007, 53.3th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Scrapy
- Scrapy Scrapy/scrapy — versions unspecified
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (leoambrus/artefactswithoutCVEonGitHubAdvisoryDatabase). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- huntr.com/bounties/27f6a021-a891-446a-ada5-0226d619dd1a (Exploit, Third Party Advisory)
- github.com/scrapy/scrapy/commit/1d0502f25bbe55a22899af915623fda1aaeb9dd8 (Patch)