CVE-2024-3572 | XML External Entity (XXE) Vulnerability in scrapy/scrapy

Exp

The scrapy/scrapy project is vulnerable to XML External Entity (XXE) attacks due to the use of lxml.etree.fromstring for parsing untrusted XML data without proper validation. This vulnerability allows attackers to perform denial of service attacks, access local files, generate network connections, or circumvent firewalls by submitting specially crafted XML data.

Published: 2024-04-16 Last update: 2025-07-28 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-3572 is rated High Exploit Risk (63.8/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.81%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-3572

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-3572

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.16% 0.81% +0.65%
2 2025-11-21 0.41% 0.16% -0.25%
3 2025-11-18 — 0.41% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-3572

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2024-3572

GitHub Security Advisory for CVE-2024-3572

GHSA-7j7m-v7m3-jqm7 · Severity: high · Ecosystem: pip — Scrapy decompression bomb vulnerability

OS Trackers for CVE-2024-3572

vendor priority summary link
debian not yet assigned CVE-2024-3572 not yet assigned priority: Debian including 1 source packages (python-scrapy), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2024-3572
ubuntu medium CVE-2024-3572 medium priority: Ubuntu including 1 source packages (python-scrapy), 10 status rows across 10 suites (bionic, focal, jammy, mantic, noble, oracular, plucky, questing, upstream, xenial): not-affected 4, released 4, ignored 2. https://ubuntu.com/security/CVE-2024-3572

Affected software / configurations for CVE-2024-3572

Vendor Product Version Raw CPE
scrapy scrapy < 2.11.1 cpe:2.3:a:scrapy:scrapy:*:*:*:*:*:*:*:*

References for CVE-2024-3572

cvelogic Threat Intelligence