scrapy
Affected
- introduced
0, fixed2.0.0, introduced2.0.0, fixed2.11.2(ecosystem)
Fixed versions
2.0.0, 2.11.2
Fix
- Fixed version
2.0.0pip install --upgrade scrapy==2.0.0 - Fixed version
2.11.2pip install --upgrade scrapy==2.11.2
Advisory
Also known as: CVE-2024-1968, GHSA-4qqq-9vqf-3h3f
The record has no summary.
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.
Not rated by the source.
0, fixed 2.0.0, introduced 2.0.0, fixed 2.11.2 (ecosystem)2.0.0, 2.11.2
2.0.0pip install --upgrade scrapy==2.0.02.11.2pip install --upgrade scrapy==2.11.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0