CVE-2024-3574
Authorization Header Leak During Cross-Domain Redirect in scrapy/scrapy
CVE-2024-3574 is an info disclosure in Scrapy Scrapy/scrapy (CVSS 7.5, High).
Public exploit available. Not confirmed exploited in the wild yet. Fixed in 2.11.1.
Public exploit: 1 sourceFix2.11.1Upgrade to this build
e.g. OID 1.3.6.1.4.1.25623.1.1.12.2025.7476.1
What to do
Find your product and version, then upgrade to the build on the right.
- Scrapy/scrapyAffected: ≥ unspecified, < 2.11.1Upgrade to: 2.11.1Stated by: CVE record
- PyPI scrapyAffected: ≥ 2, < 2.11.1Upgrade to: 2.11.1Stated by: GitHub advisory
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In scrapy version 2.10.1, an issue was identified where the Authorization header, containing credentials for server authentication, is leaked to a third-party site during a cross-domain redirect. This vulnerability arises from the failure to remove the Authorization header when redirecting across domains. The exposure of the Authorization header to unauthorized actors could potentially allow for account hijacking.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
1 source with a proof of concept or module.
Exploit links, PoCs and Metasploit modules after sign-in- EPSS
0.6% chance of exploitation activity in the next 30 days, which ranks it in the 52nd percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
The patch came 221 days before any public exploit.
- OpenVAS check added
- Public exploit / PoCsource: other
- Patch availablerecord updated
- Publishedweakness classified, att&ck mapped
Affected products
Technical detail
CVSS 3.0 vector
Open in the CVSS calculatorCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Scored 7.5 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity NoneNo integrity impact
- Availability NoneNo availability impact
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
Questions about CVE-2024-3574
- Is CVE-2024-3574 being exploited?
- Not confirmed. Public exploit code exists (1 source), but CVE-2024-3574 is not in CISA KEV. EPSS puts the chance of exploitation in the next 30 days at 0.6%.
- Which versions are affected by CVE-2024-3574?
- Scrapy/scrapy: ≥ unspecified, < 2.11.1. Scrapy: ≥ 2, < 2.11.1.
- How do I fix or mitigate CVE-2024-3574?
- Upgrade to 2.11.1 or later. The advisory is on github.com.
Last updated
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Scrapy/scrapy, not every advisory. This one: public exploit.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI