scrapy
Affected
- introduced
0, fixed2.11.2(ecosystem)
Fixed versions
2.11.2
Fix
- Fixed version
2.11.2pip install --upgrade scrapy==2.11.2
Advisory
Also known as: CVE-2024-1968, PYSEC-2024-258
Scrapy leaks the authorization header on same-domain but cross-origin redirects
Impact
Since version 2.11.1, Scrapy drops the Authorization header when a request is redirected to a different domain. However, it keeps the header if the domain remains the same but the scheme (http/https) or the port change, all scenarios where the header should also be dropped.
In the context of a man-in-the-middle attack, this could be used to get access to the value of that Authorization header
Patches
Upgrade to Scrapy 2.11.2.
Workarounds
There is no easy workaround for unpatched versions of Scrapy. You can replace the built-in redirect middlewares with custom ones patched for this issue, but you have to patch them yourself, manually.
References
This security issue was reported and fixed by @szarny at https://huntr.com/bounties/27f6a021-a891-446a-ada5-0226d619dd1a/.
Medium Basis: The source's own band: MODERATE
0, fixed 2.11.2 (ecosystem)2.11.2
2.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: GitHub Advisory Database (reviewed advisories) · CC BY 4.0