https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 17:22:33 +0000 https://cve.radiocsirt.org/vuln/brew-scrapy-cve-2022-0577 <p><strong>Affected:</strong> Homebrew: scrapy</p> <p>Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository scrapy/scrapy prior to 2.6.1.</p> <p><strong>Affected:</strong> Homebrew: scrapy</p> <p>Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository scrapy/scrapy prior to 2.6.1.</p> https://cve.radiocsirt.org/vuln/brew-scrapy-cve-2022-0577 https://cve.radiocsirt.org/vuln/cnvd-2022-17012 cnvd-2022-17012 https://cve.radiocsirt.org/vuln/cnvd-2022-17012 https://cve.radiocsirt.org/vuln/euvd-2026-11053 EUVD-2026-11053 https://cve.radiocsirt.org/vuln/euvd-2026-11053 https://cve.radiocsirt.org/vuln/fkie_cve-2022-0577 <p>Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository scrapy/scrapy prior to 2.6.1.</p> <p>Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository scrapy/scrapy prior to 2.6.1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-0577 https://cve.radiocsirt.org/vuln/ghsa-cjvr-mfj7-j4j8 <p><strong>Affected:</strong> PyPI: scrapy</p> <p>### Impact</p> <p>If you manually define cookies on a [`Request`](https://docs.scrapy.org/en/latest/topics/request-response.html#scrapy.http.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.</p> <p>### Patches</p> <p>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².</p> <p>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.</p> <p>¹ 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.</p> <p>² This prevents cookie leaks to unintended domains even if the cookies middleware is not used.</p> <p>### Workarounds</p> <p>If you cannot upgrade, set your cookies using a list of dictionaries instead of a single dictionary, as described in the [`Request` documentation](https://docs.scrapy.org/en/latest/topics/request-response.html#scrapy.http.Request), and set the right domain f…</p> <p><strong>Affected:</strong> PyPI: scrapy</p> <p>### Impact</p> <p>If you manually define cookies on a [`Request`](https://docs.scrapy.org/en/latest/topics/request-response.html#scrapy.http.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.</p> <p>### Patches</p> <p>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².</p> <p>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.</p> <p>¹ 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.</p> <p>² This prevents cookie leaks to unintended domains even if the cookies middleware is not used.</p> <p>### Workarounds</p> <p>If you cannot upgrade, set your cookies using a list of dictionaries instead of a single dictionary, as described in the [`Request` documentation](https://docs.scrapy.org/en/latest/topics/request-response.html#scrapy.http.Request), and set the right domain f…</p> https://cve.radiocsirt.org/vuln/ghsa-cjvr-mfj7-j4j8 https://cve.radiocsirt.org/vuln/gsd-2022-0577 gsd-2022-0577 https://cve.radiocsirt.org/vuln/gsd-2022-0577 https://cve.radiocsirt.org/vuln/opensuse-su-2024:11889-1 <p>python-Scrapy-doc-2.6.1-1.1 on GA media</p> <p>python-Scrapy-doc-2.6.1-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:11889-1 https://cve.radiocsirt.org/vuln/pysec-2022-159 <p><strong>Affected:</strong> PyPI: scrapy</p> <p>Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository scrapy/scrapy prior to 2.6.1.</p> <p><strong>Affected:</strong> PyPI: scrapy</p> <p>Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository scrapy/scrapy prior to 2.6.1.</p> https://cve.radiocsirt.org/vuln/pysec-2022-159 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-0577 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: python-scrapy, Ubuntu:Pro:18.04:LTS: python-scrapy, Ubuntu:Pro:20.04:LTS: python-scrapy, Ubuntu:Pro:22.04:LTS: python-scrapy</p> <p>Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository scrapy/scrapy prior to 2.6.1.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: python-scrapy, Ubuntu:Pro:18.04:LTS: python-scrapy, Ubuntu:Pro:20.04:LTS: python-scrapy, Ubuntu:Pro:22.04:LTS: python-scrapy</p> <p>Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository scrapy/scrapy prior to 2.6.1.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-0577