scrapy
Affected
- introduced
0, fixed1.8.2(ecosystem)
Fixed versions
1.8.2
Fix
- Fixed version
1.8.2pip install --upgrade scrapy==1.8.2
Advisory
Also known as: CVE-2022-0577, PYSEC-2022-159
Incorrect Authorization and Exposure of Sensitive Information to an Unauthorized Actor in scrapy
Impact
If you manually define cookies on a `Request` object, and that Request object gets a redirect response, the new Request object scheduled to follow the redirect keeps those user-defined cookies, regardless of the target domain.
Patches
Upgrade to Scrapy 2.6.0, which resets cookies when creating Request objects to follow redirects¹, and drops the Cookie header if manually-defined if the redirect target URL domain name does not match the source URL domain name².
If you are using Scrapy 1.8 or a lower version, and upgrading to Scrapy 2.6.0 is not an option, you may upgrade to Scrapy 1.8.2 instead.
¹ At that point the original, user-set cookies have been processed by the cookie middleware into the global or request-specific cookiejar, with their domain restricted to the domain of the original URL, so when the cookie middleware processes the new (redirect) request it will incorporate those cookies into the new request as long as the domain of the new request matches the domain of the original request.
² This prevents cookie leaks to unintended domains even if the cookies middleware is not used.
Workarounds
If you cannot upgrade, set your cookies using a list of dictionaries instead of a single dictionary, as described in the `Request` documentation, and set the right domain for each cookie.
Alternatively, you can disable cookies altogether, or limit target domains to domains that you trust with all your user-set cookies.
References
For more information
If you have any questions or comments about this advisory:
Medium Basis: The source's own band: MODERATE
0, fixed 1.8.2 (ecosystem)1.8.2
1.8.2pip install --upgrade scrapy==1.8.22.0.0, fixed 2.6.0 (ecosystem)2.6.0
2.6.0pip install --upgrade scrapy==2.6.0Fix 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