← Back
CVE-2024-3566
critical
CVSS 9.8
Command Injection in node (CVE-2024-3566)
Summary
command injection in node (CVE-2024-3566). Successful exploitation can lead to full system takeover. Exploitable via ``cmd.exe``. Mitigation: upgrade to `18.19.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-3566** has been found in node.
Attackers can target a specific entry point like ``cmd.exe`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade node to **18.19.0** or later.
If unsure, ask your IT team or search "node CVE-2024-3566" on the vendor's site.
CVE-2024-3566 (node) — CWE-77 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `cmd.exe` / `RawCommand` / `CreateProcess` / `lpCommandLine`
Patched: `18.19.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.
❓ What is the problem
**A vulnerability** (CWE-77) exists in node. Attackers reach the vulnerable code path via ``cmd.exe`` without authentication.
📍 Affected scope
node — . Attack surface: `cmd.exe` / `RawCommand` / `CreateProcess` / `lpCommandLine`.
🔥 Severity
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **18.19.0**.
🛡️ 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 'node' .` 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 'node' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `node` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade node to 18.19.0ステージング環境で 18.19.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
node
[{"type":"SEMVER","events":[{"introduced":"1.77.2"},{"fixed":"18.19.0"}]}]
Bitnami
node-min
[{"type":"SEMVER","events":[{"introduced":"1.77.2"},{"fixed":"18.20.5"}]}]
Hackage
process
[{"type":"ECOSYSTEM","events":[{"introduced":"1.0.0.0"},{"fixed":"1.6.23.0"}]}]
References
- advisory https://kb.cert.org/vuls/id/123335
- patch https://github.com/haskell/process/commit/3c419f9eeedac024c9dccce544e5a6fb587179a5
- patch https://github.com/haskell/process/commit/951b02dd95559b1a26f2456bfb97cf740ea40934
- patch https://github.com/haskell/process/commit/5fc91f5f36ed4479be2b95f04f264bb78ac8089d
- web https://flatt.tech/research/posts/batbadbut-you-cant-securely-execute-commands-on-windows/
- web https://learn.microsoft.com/en-us/archive/blogs/twistylittlepassagesallalike/everyone-quotes-command-line-arguments-the-wrong-way
- web https://www.cve.org/CVERecord?id=CVE-2024-1874
- web https://www.cve.org/CVERecord?id=CVE-2024-22423
- web https://www.cve.org/CVERecord?id=CVE-2024-24576
- web https://www.kb.cert.org/vuls/id/123335
- web https://github.com/nu11secur1ty/Windows11Exploits/tree/main/2024/CVE-2024-3566
- web https://nvd.nist.gov/vuln/detail/CVE-2024-3566