Cyber Resilience

CVE-2024-3566

RCE in Nodejs Node.Js ≤ 18.20.2

Public PoCRCECommand Injection
Published
10 April 2024
Modified
15 May 2026
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.069 93th percentile
Risk Priority 80 floored blend · peak EPSS

Summary

CVE-2024-3566 is a critical-severity Command Injection (CWE-77) vulnerability in Nodejs Node.Js. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A command injection vulnerability tracked as CVE-2024-3566 affects Windows applications that indirectly rely on the CreateProcess function under specific conditions. The flaw, assigned CWE-77 and carrying a CVSS 3.1 score of 9.8, enables an attacker to inject and execute arbitrary commands when those conditions are met. It impacts any software that passes untrusted input into command execution paths without adequate sanitization on Windows platforms.

An unauthenticated remote attacker can exploit the issue over the network without user interaction. Successful exploitation grants full control over the affected application, allowing arbitrary command execution that can lead to confidentiality, integrity, and availability impacts on the target system.

Public references, including research on Windows command-line handling and related CVEs such as CVE-2024-1874 and CVE-2024-22423, highlight longstanding difficulties with secure command execution and argument quoting on Windows. No specific patch details or mitigation steps are enumerated in the provided references beyond general awareness of the underlying CreateProcess behavior.

The EPSS score remains flat at 0.1055 with no material increase observed after disclosure.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

A command inject vulnerability allows an attacker to perform command injection on Windows applications that indirectly depend on the CreateProcess function when the specific conditions are satisfied.

CWE(s)
CWE-77

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
attack.mitre.org →
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
attack.mitre.org →
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
attack.mitre.org →
T1059.008 Network Device CLI Execution
Adversaries may abuse scripting or built-in command line interpreters (CLI) on network devices to execute malicious command and payloads.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-37385Same product: Microsoft Windows
CVE-2024-4944Same product: Microsoft Windows
CVE-2025-61787Same product: Microsoft Windows
CVE-2024-51736Same product: Microsoft Windows
CVE-2024-4712Same product: Microsoft Windows
CVE-2026-35558Same product: Microsoft Windows
CVE-2024-41783Same product: Microsoft Windows
CVE-2024-38228Same vendor: Microsoft
CVE-2023-21778Same vendor: Microsoft
CVE-2024-49026Same vendor: Microsoft

Affected Assets

haskell
process library
≤ 1.6.19.0
nodejs
node.js
≤ 18.20.2 · 19.0.0 — 20.12.2 · 21.0.0 — 21.7.3
php
php
≤ 8.1.28 · 8.2.0 — 8.2.18 · 8.3.0 — 8.3.6
rust-lang
rust
≤ 1.77.2
yt-dlp project
yt-dlp
2021.04.11 — 2024.04.09

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.3
  • V1.2.5
  • V1.2.8
  • V1.2.9

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover command-construction flaws before deployment.

SI-10 Information Input Validation good match

Input validation directly stops construction of commands from untrusted data containing special elements.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles include proper neutralization and safe command construction practices.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and neutralization that prevent command injection.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data can detect anomalous command execution resulting from injection.

ID.RA-01 partial match
prevents

Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.28 Secure coding mostly match
prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches command-injection vulnerabilities before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection flaws including command injection.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.

A.8.31 Separation of development, test and production environments none match
none

Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.

References