What is CVE-2018-6342?

CVE-2018-6342 is a high-severity OS command injection vulnerability in react-dev-utils (npm), affecting versions >= 1.0.0, < 1.0.4. It is fixed in 1.0.4, 2.0.2, 3.1.2, 4.2.2, 5.0.2. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.

Which versions of react-dev-utils are affected by CVE-2018-6342?

react-dev-utils (npm) versions >= 1.0.0, < 1.0.4 is affected.

Is there a fix for CVE-2018-6342?

Yes. CVE-2018-6342 is fixed in 1.0.4, 2.0.2, 3.1.2, 4.2.2, 5.0.2. Upgrade to this version or later.

Is CVE-2018-6342 exploitable, and should I be worried?

Whether CVE-2018-6342 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2018-6342 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2018-6342?

Upgrade: react-dev-utils to 1.0.4 or later, react-dev-utils to 2.0.2 or later, react-dev-utils to 3.1.2 or later, react-dev-utils to 4.2.2 or later, react-dev-utils to 5.0.2 or later.

CVE-2018-6342 in react-dev-utils

Q: Which versions of react-dev-utils are affected by CVE-2018-6342?

react-dev-utils (npm) versions >= 1.0.0, < 1.0.4 is affected.

Q: Is there a fix for CVE-2018-6342?

Yes. CVE-2018-6342 is fixed in 1.0.4, 2.0.2, 3.1.2, 4.2.2, 5.0.2. Upgrade to this version or later.

Q: Is CVE-2018-6342 exploitable, and should I be worried?

Whether CVE-2018-6342 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2018-6342 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2018-6342?

Upgrade: react-dev-utils to 1.0.4 or later, react-dev-utils to 2.0.2 or later, react-dev-utils to 3.1.2 or later, react-dev-utils to 4.2.2 or later, react-dev-utils to 5.0.2 or later.

Summary

react-dev-utils on Windows vulnerable to Remote Code Execution

react-dev-utils on Windows is vulnerable to remote code execution.

Impact

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

Affected versions

react-dev-utils (>= 1.0.0, < 1.0.4) react-dev-utils (>= 2.0.0, < 2.0.2) react-dev-utils (>= 3.0.0, < 3.1.2) react-dev-utils (>= 4.0.0, < 4.2.2) react-dev-utils (>= 5.0.0, < 5.0.2)

Security releases

react-dev-utils → 1.0.4 (npm) react-dev-utils → 2.0.2 (npm) react-dev-utils → 3.1.2 (npm) react-dev-utils → 4.2.2 (npm) react-dev-utils → 5.0.2 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Update to one of the following versions, depending on the release line that you are using.

1.0.4
2.0.2
3.1.2
4.2.2
5.0.2
6.0.0-next.a671462c

Frequently Asked Questions

What is CVE-2018-6342? CVE-2018-6342 is a high-severity OS command injection vulnerability in react-dev-utils (npm), affecting versions >= 1.0.0, < 1.0.4. It is fixed in 1.0.4, 2.0.2, 3.1.2, 4.2.2, 5.0.2. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
Which versions of react-dev-utils are affected by CVE-2018-6342? react-dev-utils (npm) versions >= 1.0.0, < 1.0.4 is affected.
Is there a fix for CVE-2018-6342? Yes. CVE-2018-6342 is fixed in 1.0.4, 2.0.2, 3.1.2, 4.2.2, 5.0.2. Upgrade to this version or later.
Is CVE-2018-6342 exploitable, and should I be worried? Whether CVE-2018-6342 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2018-6342 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2018-6342?
- Upgrade react-dev-utils to 1.0.4 or later
- Upgrade react-dev-utils to 2.0.2 or later
- Upgrade react-dev-utils to 3.1.2 or later
- Upgrade react-dev-utils to 4.2.2 or later
- Upgrade react-dev-utils to 5.0.2 or later

Other vulnerabilities in react-dev-utils

CVE-IDSeverityPackage summary

CVE-2021-24033Mediumreact-dev-utils: react-dev-utils OS Command Injection in function `getProcessForPort`