CVE-2024-3572: Scrapy Scrapy Decompression Bomb Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-7j7m-v7m3-jqm7
Share
CVSS 7.5
CWE-409
Published
Advisory Summary

CVE-2024-3572 is a HIGH (CVSS 7.5) scrapy decompression bomb vulnerability vulnerability (CWE-409: Improper Handling of Highly Compressed Data (Data Amplification)) affecting Scrapy libraries in the PyPI ecosystem. The issue involves scrapy decompression bomb vulnerability. Remediation is available by upgrading affected packages to version 2.11.1, 1.8.4.

CVE-2024-3572 at a Glance

CVE Identifier CVE-2024-3572
GHSA Identifier GHSA-7j7m-v7m3-jqm7
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-409: Improper Handling of Highly Compressed Data (Data Amplification)
Affected Product Scrapy
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2024-3572

To remediate this vulnerability, upgrade all affected Scrapy dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

scrapy fixed: 2.11.1 
pip install scrapy>=2.11.1
scrapy fixed: 1.8.4 
pip install scrapy>=1.8.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show scrapy

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2024-3572, inspect your installed packages using pip:

pip show scrapy

Analyze the terminal output to locate any version of Scrapy in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.11.1), your application is affected.

Note: The pip show scrapy command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-409: Improper Handling of Highly Compressed Data (Data Amplification), where the product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output. In Scrapy, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Scrapy limits allowed response sizes by default through the [`DOWNLOAD_MAXSIZE`](https://docs.scrapy.org/en/latest/topics/settings.html#download-maxsize) and [`DOWNLOAD_WARNSIZE`](https://docs.scrapy.org/en/latest/topics/settings.html#download-warnsize) settings. However, those limits were only being enforced during the download of the raw, usually-compressed response bodies, and not during decompression, making Scrapy vulnerable to [decompression bombs](https://cwe.mitre.org/data/definitions/409.html). A malicious website being scraped could send a small response that, on decompression, could exhaust the memory available to the Scrapy process, potentially affecting any other process sharing that memory, and affecting disk usage in case of uncompressed response caching. ### Patches Upgrade to Scrapy 2.11.1. If you are using Scrapy 1.8 or a lower version, and upgrading to Scrapy 2.11.1 is not an option, you may upgrade to Scrapy 1.8.4 instead. ### Workarounds There is no easy workaround. Disabling HTTP decompression altogether is impractical, as HTTP compression is a rather common practice. However, it is technically possible to manually backport the 2.11.1 or 1.8.4 fix, replacing the corresponding components of an unpatched version of Scrapy with patched versions copied into your own code. ### Acknowledgements This security issue was reported by @dmandefy [through huntr.com](https://huntr.com/bounties/c4a0fac9-0c5a-4718-9ee4-2d06d58adabb/).

CVE-2024-3572 Affected Scrapy Versions

2 component(s)
Fixed Versions:
2.11.11.8.4
Product / Package Ecosystem Affected Versions Fixed Version
scrapy
pypi/scrapy
PyPI
≥ 2.0.0
< 2.11.1
2.11.1
scrapy
pypi/scrapy
PyPI
< 1.8.4
1.8.4

References

GitHub Advisory / Wiki ADVISORY
https://github.com/scrapy/scrapy/security/advisories/GHSA-7j7m-v7m3-jqm7
NVD — CVE-2024-3572 NVD
https://nvd.nist.gov/vuln/detail/CVE-2024-3572
Security Fix Commit FIX COMMIT
https://github.com/scrapy/scrapy/commit/71b8741e3607cfda2833c7624d4ada87071aa8e5
Security Fix Commit FIX COMMIT
https://github.com/scrapy/scrapy/commit/809bfac4890f75fc73607318a04d2ccba71b3d9f
Scrapy Security Information SECURITY
https://docs.scrapy.org/en/latest/news.html#scrapy-2-11-1-2024-02-14
Scrapy Source Repository REPOSITORY
https://github.com/scrapy/scrapy
huntr.com/bounties/c4a0fac9-0... WEB
https://huntr.com/bounties/c4a0fac9-0c5a-4718-9ee4-2d06d58adabb

Frequently Asked Questions

What is CVE-2024-3572?
CVE-2024-3572 is a security vulnerability in Scrapy involving Scrapy decompression bomb vulnerability under CWE-409: Improper Handling of Highly Compressed Data (Data Amplification).
Which Scrapy versions are affected?
Affected versions include releases prior to 2.11.1, 1.8.4 across affected packages: scrapy.
What version fixes CVE-2024-3572?
Upgrading to 2.11.1, 1.8.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is scrapy affected?
Yes, scrapy is affected in releases prior to 2.11.1, 1.8.4. Upgrade your dependency to 2.11.1, 1.8.4 or later.
What is the CVSS score of CVE-2024-3572?
CVE-2024-3572 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2024-3572?
CVE-2024-3572 is classified under CWE-409: Improper Handling of Highly Compressed Data (Data Amplification) (The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.).
How can I check PyPI dependencies for CVE-2024-3572?
Run the dependency tree command: 'pip show scrapy'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-7j7m-v7m3-jqm7",
  "modified" : "2024-04-16T14:05:17Z",
  "published" : "2024-02-16T16:07:13Z",
  "aliases" : [ "CVE-2024-3572" ],
  "summary" : "Scrapy decompression bomb vulnerability",
  "details" : "### Impact\n\nScrapy limits allowed response sizes by default through the [`DOWNLOAD_MAXSIZE`](https://docs.scrapy.org/en/latest/topics/settings.html#download-maxsize) and [`DOWNLOAD_WARNSIZE`](https://docs.scrapy.org/en/latest/topics/settings.html#download-warnsize) settings.\n\nHowever, those limits were only being enforced during the download of the raw, usually-compressed response bodies, and not during decompression, making Scrapy vulnerable to [decompression bombs](https://cwe.mitre.org/data/definitions/409.html).\n\nA malicious website being scraped could send a small response that, on decompression, could exhaust the memory available to the Scrapy process, potentially affecting any other process sharing that memory, and affecting disk usage in case of uncompressed response caching.\n\n### Patches\n\nUpgrade to Scrapy 2.11.1.\n\nIf you are using Scrapy 1.8 or a lower version, and upgrading to Scrapy 2.11.1 is not an option, you may upgrade to Scrapy 1.8.4 instead.\n\n### Workarounds\n\nThere is no easy workaround.\n\nDisabling HTTP decompression altogether is impractical, as HTTP compression is a rather common practice.\n\nHowever, it is technically possible to manually backport the 2.11.1 or 1.8.4 fix, replacing the corresponding components of an unpatched version of Scrapy with patched versions copied into your own code.\n\n### Acknowledgements\n\nThis security issue was reported by @dmandefy  [through huntr.com](https://huntr.com/bounties/c4a0fac9-0c5a-4718-9ee4-2d06d58adabb/).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "scrapy"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.11.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "scrapy"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.8.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/scrapy/scrapy/security/advisories/GHSA-7j7m-v7m3-jqm7"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-3572"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/scrapy/scrapy/commit/71b8741e3607cfda2833c7624d4ada87071aa8e5"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/scrapy/scrapy/commit/809bfac4890f75fc73607318a04d2ccba71b3d9f"
  }, {
    "type" : "WEB",
    "url" : "https://docs.scrapy.org/en/latest/news.html#scrapy-2-11-1-2024-02-14"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/scrapy/scrapy"
  }, {
    "type" : "WEB",
    "url" : "https://huntr.com/bounties/c4a0fac9-0c5a-4718-9ee4-2d06d58adabb"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-409" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-02-16T16:07:13Z",
    "nvd_published_at" : null
  }
}