# CVE-2024-1892: ReDoS Vulnerability in scrapy/scrapy's XMLFeedSpider

> Attackers can cause denial of service in Scrapy's XMLFeedSpider by crafting malicious XML content that triggers inefficient regular expression processing.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Feb 2024
- **Updated:** 11 Aug 2024
- **Also known as:** DEBIAN-CVE-2024-1892, GHSA-cc65-xxvf-f7r9, PYSEC-2024-162, UBUNTU-CVE-2024-1892, openSUSE-SU-2024:13802-1

## What is CVE-2024-1892?

CVE-2024-1892 is a high-severity denial of service vulnerability in scrapy/scrapy, published on 28 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2024-1892?

5 open source packages ship an affected version, including scrapy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `scrapy` | PyPI | All versions | 1.8.4 |
| `scrapy` | PyPI | All versions | 1.8.4 |
| `scrapy` | PyPI | All versions | 2.11.1 |
| `scrapy` | PyPI | From 2 | 2.11.1 |
| `scrapy` | PyPI | From 2 | 2.11.1 |

Products: Scrapy Scrapy.

## How do I fix CVE-2024-1892?

Upgrade scrapy to a fixed version for your release line: 1.8.4 or 2.11.1.

## Is CVE-2024-1892 being exploited?

There is no known exploitation of CVE-2024-1892 in the wild and no public exploit code.

## Other vulnerabilities in scrapy/scrapy

- [CVE-2024-1968](https://insights.sbomify.com/CVE-2024-1968/): Authorization Header Leakage in scrapy/scrapy on Scheme Change Redirects (high 7.5)
- [CVE-2024-3572](https://insights.sbomify.com/CVE-2024-3572/): XML External Entity (XXE) Vulnerability in scrapy/scrapy (high 7.5)
- [CVE-2024-3574](https://insights.sbomify.com/CVE-2024-3574/): Authorization Header Leak During Cross-Domain Redirect in scrapy/scrapy (high 7.5)
- [CVE-2017-14158](https://insights.sbomify.com/CVE-2017-14158/): Scrapy denial of service vulnerability (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1892 and fix it if it is affected.

What it is: CVE-2024-1892 is a high-severity denial of service vulnerability in scrapy/scrapy, published on 28 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1892 in the wild and no public exploit code.

Affected packages and fixed versions:
- scrapy (PyPI): affected all versions; fixed in 1.8.4
- scrapy (PyPI): affected all versions; fixed in 1.8.4
- scrapy (PyPI): affected all versions; fixed in 2.11.1
- scrapy (PyPI): affected from 2; fixed in 2.11.1
- scrapy (PyPI): affected from 2; fixed in 2.11.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-1892/ (Markdown: https://insights.sbomify.com/CVE-2024-1892/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1892
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1892
- OSV: https://osv.dev/vulnerability/CVE-2024-1892

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-1892/
Summaries are generated and may contain mistakes; the official description above is the record.