Vulnerability in distributed (CVE-2021-42343)
Summary
Vulnerability in distributed (CVE-2021-42343). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2021.10.0 or later.
Original description
The description as published by the source.
An issue was discovered in the Dask distributed package before 2021.10.0 for Python. Single machine Dask clusters started with dask.distributed.LocalCluster or dask.distributed.Client (which defaults to using LocalCluster) would mistakenly configure their respective Dask workers to listen on external interfaces (typically with a randomly selected high port) rather than only on localhost. A Dask cluster created using this method (when running on a machine that has an applicable port exposed) could be used by a sophisticated attacker to achieve remote code execution.
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-42343 has been found in distributed.
Successful exploitation can lead to full system takeover.
What to do: upgrade distributed to 2021.10.0 or later.
If unsure, ask your IT team or search "distributed CVE-2021-42343" on the vendor's site.
CVE-2021-42343 (distributed) — CWE-668
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2021.10.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.
A vulnerability (CWE-668) exists in distributed.
Check the vendor advisory for the affected versions of distributed.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2021.10.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 'distributed' . 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 'distributed' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
distributedを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade distributed to 2021.10.0ステージング環境で 2021.10.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2021-42343 dask.distributed Fixed in: 2021.09.1+ds.1-2
References
- advisory github.com
- advisory nvd.nist.gov
- advisory docs.dask.org
- advisory github.com
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com