CVE-2024-1968
A public proof of concept exists; no exploitation attested.
- Published2024-05-20
- Fixed in2.11.2 · 2.0.0
- WeaknessCWE-200
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2024-05-2008:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-28 15:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-1968?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-1968?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV · CISA-ADP| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.x | ≥ 2.0.0, < 2.11.2 | 2.11.2 | NVD · OSV |
| 2.11 | < 2.11.2 | 2.11.2 | CISA-ADP · OSV |
| 2.0 | < 2.0.0 | 2.0.0 | OSV |
| 1.8 | ≤ 1.8.4 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
- CVE-2024-1968 Red Hat Product Security
python-scrapy: sensitive information disclosure
Fix
- Update Scrapy to 2.11.2 · 2.0.0
Advisories and patches
- github.comPatch
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- 2024-05-20
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2024-1968?
Is CVE-2024-1968 actively exploited?
What is the CVSS score for CVE-2024-1968?
Running scrapy? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.