CVE-2024-27980
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDue to the improper handling of batch files in child_process.spawn / child_process.spawnSync, a malicious command line argument can inject arbitrary commands and achieve code execution even if the shell option is not enabled.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a command injection vulnerability in Node.js child_process module where batch file handling (.bat, .cmd) in spawn/spawnSync allows malicious command line arguments to inject arbitrary commands and achieve code execution even when the shell option is set to false. The vulnerability stems from improper handling of batch file arguments on Windows systems.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Windows environmentRun 'node -e "console.log(process.platform)"' and verify the output is 'win32'Affected if The platform is not Windows - this vulnerability only affects Windows systems
-
Check Node.js versionRun 'node -v' to get the installed version. Compare against the affected unpatched versions for your Node.js release lineAffected if Running an unpatched Node.js version that has not addressed the batch file argument injection flaw
-
Identify spawn/spawnSync usage with batch filesSearch codebase for calls to child_process.spawn() or child_process.spawnSync() that reference .bat or .cmd files (e.g., 'somefile.bat', 'script.cmd')Affected if Code uses spawn or spawnSync with .bat or .cmd file extensions on Windows
-
Verify shell option is set to falseInspect spawn/spawnSync calls and check if the options object contains 'shell: false'Affected if The shell option is explicitly set to false - this configuration is vulnerable and was intended to be the safe setting
-
Inspect arguments passed to batch file spawnsReview the arguments array passed to spawn/spawnSync calls involving .bat/.cmd files for any unsanitized user input or shell metacharactersAffected if Arguments contain unsanitized input, especially if derived from user input or external sources
You are affected if running Node.js on Windows with an unpatched version and your application uses child_process spawn/spawnSync to execute .bat or .cmd files with the shell option set to false, particularly when passing unsanitized arguments.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Node.js to a patched version that properly sanitizes batch file arguments in child_process functions, or implement strict input validation on all arguments passed to spawn/spawnSync when working with batch files on Windows.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27980 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-27980 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data