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.
Original description
The description as published by the source.
process: command injection via argument list on Windows
The process library on Windows is vulnerable to a command injection
vulnerability, via cmd.exe's interpretation of arguments. Programs that
invoke batch files (.bat, .cmd) and pass arguments whose values are
affected by program inputs may be affected.
This issue was discovered in many programming languages' Windows process
execution behaviour. It was tracked by CERT/CC as VU#123335 and a
coordinated disclosure was made on 2024-04-09 17:00 UTC.
A fix was released in process-1.6.19.0.
Background
Unlike POSIX systems, Windows does not have a mechanism for passing multiple
arguments.Command line parsing is up to individual programs.
The process library defines the RawCommand constructor for specifying an
executable and its arguments:
data CmdSpec
= ShellCommand String
| RawCommand FilePath [String]
On Windows, the RawCommand executable name and arguments are serialised into
a single command line string, with separate arguments quoted separately.
process then invokes the Windows CreateProcess
routine with this command line string is given as the lpCommandLine
argument.
Issue
When executing .bat or .cmd files, CreateProcess
implicitly spawns cmd.exe. The System.Process command line c…
Source: NIST National Vulnerability Database NVD
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-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.
A vulnerability (CWE-77) exists in node. Attackers reach the vulnerable code path via cmd.exe without authentication.
Check the vendor advisory for the affected versions of node. Attack surface: cmd.exe / RawCommand / CreateProcess / lpCommandLine.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 18.19.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 'node' . 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 'node' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nodeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade node to 18.19.0ステージング環境で 18.19.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory kb.cert.org
- patch github.com
- patch github.com
- patch github.com
- web flatt.tech
- web learn.microsoft.com
- web cve.org
- web cve.org
- web cve.org
- web kb.cert.org
- web github.com
- web nvd.nist.gov