CVE-2024-1968Sensitive Information Exposure in Scrapy

Severity
7.5HIGHNVD
OSV6.5
EPSS
0.2%
top 59.17%
CISA KEV
Not in KEV
Exploit
No known exploits
Timeline
PublishedMay 20
Latest updateMay 5

Description

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 potenti

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitability: 3.9 | Impact: 3.6

Affected Packages4 packages

NVDscrapy/scrapy2.0.02.11.2+1
PyPIscrapy/scrapy< 2.11.2
CVEListV5scrapy/scrapy_scrapyunspecified2.11.2
debiandebian/python-scrapy< python-scrapy 2.11.2-1 (forky)

Patches

🔴Vulnerability Details

4
OSV
python-scrapy vulnerabilities2025-05-05
OSV
CVE-2024-1968: In scrapy/scrapy, an issue was identified where the Authorization header is not removed during redirects that only change the scheme (e2024-05-20
GHSA
Scrapy leaks the authorization header on same-domain but cross-origin redirects2024-05-14
OSV
Scrapy leaks the authorization header on same-domain but cross-origin redirects2024-05-14

📋Vendor Advisories

2
Ubuntu
Scrapy vulnerabilities2025-05-05
Debian
CVE-2024-1968: python-scrapy - In scrapy/scrapy, an issue was identified where the Authorization header is not ...2024