CVE-2024-1968
Scrapy leaks the authorization header on same-domain but cross-origin redirects
Description
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.
How to fix CVE-2024-1968
To remediate CVE-2024-1968, upgrade the affected package to a fixed version below.
- —no fix listed
- —upgrade to 2.11.2 or later
- —upgrade to 1d0502f25bbe55a22899af915623fda1aaeb9dd8 or later
Is CVE-2024-1968 being exploited?
Low — EPSS is 0.2%, meaning exploitation activity has not been observed at scale.
Affected packages (3)
- from 0
- from 0, < 2.11.2
- from 0, < 1d0502f25bbe55a22899af915623fda1aaeb9dd8 | from 0, < 2.0.0, >= 2.0.0, < 2.11.2
CVSS scores
| Source | Version | Severity | Vector |
|---|---|---|---|
| osv | CVSS 3.1 | MEDIUM5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |