Skip to content
Fencer Intel
high 8.1

CVE-2024-27980 json

Due to the improper handling of batch files in child_process.spawn / child_process.spawnSync, a malicious command line argument can inject…

published last yr. modified 4mo ago also BIT-node-2024-27980 , BIT-node-min-2024-27980 , EUVD-2024-25154

cvss
8.1
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

Due 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.

Patch / fix

  • bitnami node 18.20.2, 20.12.2, 21.7.3
  • bitnami node-min 18.20.2, 20.12.2, 21.7.3
  • NodeJS Node 18.20.2, 20.12.2, 21.7.3
  • nodejs20 SLE Module for Web and Scripting 15 SP6, openSUSE Leap 15.6 20.15.1-150600.3.3.2
  • nodejs20 SLE Module for Web and Scripting 15 SP5, openSUSE Leap 15.5 20.15.1-150500.11.12.2
  • nodejs18 SLE Module for Web and Scripting 15 SP5, openSUSE Leap 15.5 18.20.4-150400.9.24.2
  • nodejs18 SLE Module for Web and Scripting 12 18.20.4-8.24.1

suse advisories SUSE-SU-2024:2574-1SUSE-SU-2024:2543-1SUSE-SU-2024:2542-1SUSE-SU-2024:2496-1

  • nodejs20 openSUSE Tumbleweed 20.15.1-1.1
  • nodejs21 openSUSE Tumbleweed 21.7.3-1.1

opensuse advisories openSUSE-SU-2024:14214-1openSUSE-SU-2024:14025-1

Is CVE-2024-27980 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-27980 updated

Node.js: Fail to Escape Arguments Properly in Microsoft Windows

  • Red Hat Enterprise Linux 8 npm, nodejs, nodejs-libs, nodejs-nodemon, nodejs-full-i18n, nodejs-packaging, +1 more Red Hat Enterprise Linux 9 npm, nodejs, nodejs-libs, nodejs-full-i18n
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

1.40% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami node
<18.20.2
>=19.0.0, <20.12.2
>=21.0.0, <21.7.3
18.20.2
20.12.2
21.7.3
bitnami node-min
<18.20.2
>=19.0.0, <20.12.2
>=21.0.0, <21.7.3
18.20.2
20.12.2
21.7.3

Affected products

  • NodeJS Node

Classification

Weakness
  • CWE-77 Improper Neutralization of Special Elements used in a Command
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.