← Back
ALPINE-CVE-2021-42383
Vulnerability in busybox (ALPINE-CVE-2021-42383)
Summary
vulnerability in busybox (ALPINE-CVE-2021-42383). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `1.31.1-r11` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **ALPINE-CVE-2021-42383** has been found in busybox.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade busybox to **1.31.1-r11** or later.
If unsure, ask your IT team or search "busybox ALPINE-CVE-2021-42383" on the vendor's site.
ALPINE-CVE-2021-42383 (busybox) —
Attack vector: remote (network-reachable) / no user interaction
Patched: `1.31.1-r11` — 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** (unclassified) exists in busybox.
📍 Affected scope
busybox — .
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **1.31.1-r11**.
🛡️ 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 'busybox' .` 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 'busybox' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `busybox` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade busybox to 1.31.1-r11ステージング環境で 1.31.1-r11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Alpine:v3.11
busybox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.31.1-r11"}]}]
Alpine:v3.12
busybox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.31.1-r21"}]}]
Alpine:v3.13
busybox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.32.1-r7"}]}]
Alpine:v3.14
busybox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.33.1-r6"}]}]
Alpine:v3.15
busybox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34.0-r0"}]}]
Alpine:v3.16
busybox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34.0-r0"}]}]
Alpine:v3.17
busybox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34.0-r0"}]}]
Alpine:v3.18
busybox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34.0-r0"}]}]
Alpine:v3.19
busybox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34.0-r0"}]}]
Alpine:v3.20
busybox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34.0-r0"}]}]
Alpine:v3.21
busybox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34.0-r0"}]}]
Alpine:v3.22
busybox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34.0-r0"}]}]
Alpine:v3.23
busybox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34.0-r0"}]}]
Alpine:v3.24
busybox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.34.0-r0"}]}]