Information Exposure Affecting python-scrapy package, versions <2.11.2-1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIANUNSTABLE-PYTHONSCRAPY-6968857
- published22 May 2024
- disclosed20 May 2024
Introduced: 20 May 2024
CVE-2024-1968 (opens in a new tab)How to fix?
Upgrade Debian:unstable python-scrapy to version 2.11.2-1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream python-scrapy package and not the python-scrapy package as distributed by Debian.
See How to fix? for Debian:unstable relevant fixed versions and status.
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.