Skip to content
Fencer Intel
medium 5.6

CVE-2021-24033 json

react-dev-utils OS Command Injection in function `getProcessForPort`

published 5y ago modified 4mo ago also GHSA-5q6m-3h65-w53x , EUVD-2021-0612

cvss
5.6
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.3%
EPSS 3.3% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

react-dev-utils prior to v11.0.4 exposes a function, getProcessForPort, where an input argument is concatenated into a command string to be executed. This function is typically used from react-scripts (in Create React App projects), where the usage is safe. Only when this function is manually invoked with user-provided values (ie: by custom code) is there the potential for command injection. If you're consuming it from react-scripts then this issue does not affect you.

Patch / fix

  • npm react-dev-utils 11.0.4
  • Facebook react-dev-utils 11.0.4

Is CVE-2021-24033 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-2021-24033 updated cvss 5.6

nodejs-react-dev-utils: function getProcessForPort concatenates input argument into a command string

  • Red Hat Decision Manager 7 react-dev-utils Red Hat Process Automation 7 react-dev-utils
    affected: no fix planned “Out of support scope”
  • Red Hat OpenShift Service Mesh 1 servicemesh-grafana, servicemesh-prometheus, servicemesh-grafana-prometheus Red Hat OpenShift Service Mesh 2.0 servicemesh-grafana, servicemesh-prometheus, servicemesh-grafana-prometheus Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/console-rhel8, rhacm2/search-ui-rhel8 Red Hat OpenShift Container Platform 4 openshift4/ose-grafana, openshift4/ose-prometheus, openshift4/ose-thanos-rhel8
    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

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/facebook/create-react-app/pull/10644 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.6 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.1 5.6 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
npm react-dev-utils
>=0.4.0, <11.0.4
11.0.4

Affected products

  • Facebook react-dev-utils

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command

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.