Information Disclosure in scrapy-splash (CVE-2021-41124)
Summary
Vulnerability in scrapy-splash (CVE-2021-41124). Confidential information can be exposed externally. Exploitable via HttpAuthMiddleware. Mitigation: upgrade to 0.8.0 or later.
Original description
The description as published by the source.
Impact
If you use HttpAuthMiddleware (i.e. the http_user and http_pass spider attributes) for Splash authentication, any non-Splash request will expose your credentials to the request target. This includes robots.txt requests sent by Scrapy when the ROBOTSTXT_OBEY setting is set to True.
Patches
Upgrade to scrapy-splash 0.8.0 and use the new SPLASH_USER and SPLASH_PASS settings instead to set your Splash authentication credentials safely.
Workarounds
If you cannot upgrade, set your Splash request credentials on a per-request basis, using the splash_headers request parameter, instead of defining them globally using the HttpAuthMiddleware.
Alternatively, make sure all your requests go through Splash. That includes disabling the robots.txt middleware.
For more information
If you have any questions or comments about this advisory:
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-41124 has been found in scrapy-splash.
Attackers can target a specific entry point like HttpAuthMiddleware over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade scrapy-splash to 0.8.0 or later.
If unsure, ask your IT team or search "scrapy-splash CVE-2021-41124" on the vendor's site.
CVE-2021-41124 (scrapy-splash) — CWE-200
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: HttpAuthMiddleware / http_user / http_pass / robots.txt
Patched: 0.8.0 — 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.
Information disclosure (CWE-200) exists in scrapy-splash. Attackers reach the vulnerable code path via HttpAuthMiddleware without authentication.
Check the vendor advisory for the affected versions of scrapy-splash. Attack surface: HttpAuthMiddleware / http_user / http_pass / robots.txt.
Severity: ?. Confidential information can be exposed externally.
Update to 0.8.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'scrapy-splash' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'scrapy-splash' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
scrapy-splashを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade scrapy-splash to 0.8.0ステージング環境で 0.8.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com