← Back
CVE-2024-3572
Vulnerability in scrapy (CVE-2024-3572)
Summary
vulnerability in scrapy (CVE-2024-3572). Risk of unauthorized operations or information disclosure. Exploitable via ``DOWNLOAD_MAXSIZE``. Mitigation: upgrade to `1.8.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-3572** has been found in scrapy.
Attackers can target a specific entry point like ``DOWNLOAD_MAXSIZE`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade scrapy to **1.8.4** or later.
If unsure, ask your IT team or search "scrapy CVE-2024-3572" on the vendor's site.
CVE-2024-3572 (scrapy) — CWE-409 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `DOWNLOAD_MAXSIZE` / `DOWNLOAD_WARNSIZE`
Patched: `1.8.4` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-409) exists in scrapy. Attackers reach the vulnerable code path via ``DOWNLOAD_MAXSIZE`` without authentication.
📍 Affected scope
scrapy — . Attack surface: `DOWNLOAD_MAXSIZE` / `DOWNLOAD_WARNSIZE`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.8.4**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'scrapy' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'scrapy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `scrapy` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade scrapy to 1.8.4ステージング環境で 1.8.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
scrapy
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.8.4"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-3572
- advisory https://github.com/advisories/GHSA-7j7m-v7m3-jqm7
- package https://github.com/scrapy/scrapy
- package https://pypi.org/project/scrapy
- web https://github.com/scrapy/scrapy/security/advisories/GHSA-7j7m-v7m3-jqm7
- web https://github.com/scrapy/scrapy/commit/71b8741e3607cfda2833c7624d4ada87071aa8e5
- web https://github.com/scrapy/scrapy/commit/809bfac4890f75fc73607318a04d2ccba71b3d9f
- web https://docs.scrapy.org/en/latest/news.html#scrapy-2-11-1-2024-02-14
- web https://huntr.com/bounties/c4a0fac9-0c5a-4718-9ee4-2d06d58adabb