scrapy
Affected
- introduced
0, fixed1.8.4, introduced2, fixed2.11.1(ecosystem)
Fixed versions
1.8.4, 2.11.1
Fix
- Fixed version
1.8.4pip install --upgrade scrapy==1.8.4 - Fixed version
2.11.1pip install --upgrade scrapy==2.11.1
Advisory
Also known as: CVE-2024-3574, GHSA-cw9j-q3vf-hrrv
Scrapy authorization header leakage on cross-domain redirect
Impact
When you send a request with the Authorization header to one domain, and the response asks to redirect to a different domain, Scrapy’s built-in redirect middleware creates a follow-up redirect request that keeps the original Authorization header, leaking its content to that second domain.
The right behavior would be to drop the Authorization header instead, in this scenario.
Patches
Upgrade to Scrapy 2.11.1.
If you are using Scrapy 1.8 or a lower version, and upgrading to Scrapy 2.11.1 is not an option, you may upgrade to Scrapy 1.8.4 instead.
Workarounds
If you cannot upgrade, make sure that you are not using the Authentication header, either directly or through some third-party plugin.
If you need to use that header in some requests, add "dont_redirect": True to the request.meta dictionary of those requests to disable following redirects for them.
If you need to keep (same domain) redirect support on those requests, make sure you trust the target website not to redirect your requests to a different domain.
Acknowledgements
This security issue was reported by @ranjit-git through huntr.com.
High Basis: CVSS v3 score 7.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
0, fixed 1.8.4, introduced 2, fixed 2.11.1 (ecosystem)1.8.4, 2.11.1
1.8.4pip install --upgrade scrapy==1.8.42.11.1pip install --upgrade scrapy==2.11.1Fix 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