CVE Tools

CVE-2024-1892

ReDoS Vulnerability in scrapy/scrapy's XMLFeedSpider

CVE-2024-1892 affects Scrapy Scrapy/scrapy (CVSS 6.5, Medium).

Public exploit available. Not confirmed exploited in the wild yet. Fixed versions are out.

Check it yourself

OpenVAS · 2 checks

e.g. OID 1.3.6.1.4.1.25623.1.1.12.2025.7476.1

Run the check

Published Updated Sources: CVE.org, NVD, GitHub

What to do

Find your product and version, then upgrade to the build on the right.

  • Scrapy/scrapyAffected: ≥ unspecified, < 2.11Upgrade to: 2.11Stated 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

A Regular Expression Denial of Service (ReDoS) vulnerability exists in the XMLFeedSpider class of the scrapy/scrapy project, specifically in the parsing of XML content. By crafting malicious XML content that exploits inefficient regular expression complexity used in the parsing process, an attacker can cause a denial-of-service (DoS) condition. This vulnerability allows for the system to hang and consume significant resources, potentially rendering services that utilize Scrapy for XML processing unresponsive.

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.

EPSS47th
Public exploit
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 47th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

The patch came 420 days before any public exploit.

  1. OpenVAS check added
  2. Public exploit / PoCsource: other
  3. Patch availablerecord updated
  4. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Scored 6.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 RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity NoneNo integrity impact
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Questions about CVE-2024-1892

Is CVE-2024-1892 being exploited?
Not confirmed. Public exploit code exists (1 source), but CVE-2024-1892 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-1892?
Scrapy/scrapy: ≥ unspecified, < 2.11. Scrapy: ≥ 2, < 2.11.1.
How do I fix or mitigate CVE-2024-1892?
Upgrade to a fixed build for your product branch: 2.11, 2.11.1. 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.