CVE-2018-6342

9.8 CRITICAL

📋 TL;DR

CVE-2018-6342 is a command injection vulnerability in react-dev-utils on Windows systems. It allows attackers to execute arbitrary commands on the targeted system by sending malicious network requests to the local development server. This affects developers using vulnerable versions of react-dev-utils in their React development environments.

💻 Affected Systems

Products:
  • react-dev-utils
Versions: 1.x.x prior to 1.0.4, 2.x.x prior to 2.0.2, 3.x.x prior to 3.1.2, 4.x.x prior to 4.2.2, 5.x.x prior to 5.0.2
Operating Systems: Windows
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects Windows systems. The vulnerability exists in the local development server functionality that accepts commands to launch editors.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full system compromise with attacker gaining complete control over the developer's machine, potentially leading to data theft, ransomware deployment, or lateral movement within the network.

🟠

Likely Case

Local privilege escalation allowing attackers to execute commands with the privileges of the development server process, potentially accessing sensitive development files and credentials.

🟢

If Mitigated

No impact if the development server is not running or is properly firewalled from untrusted networks.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires network access to the development server (port 3000 by default). The vulnerability is in the editor launch command handler that doesn't properly sanitize input.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: react-dev-utils >=1.0.4, >=2.0.2, >=3.1.2, >=4.2.2, >=5.0.2

Vendor Advisory: https://github.com/facebook/create-react-app/releases/tag/v1.1.5

Restart Required: Yes

Instructions:

1. Update react-dev-utils to patched version: npm update react-dev-utils 2. Verify version: npm list react-dev-utils 3. Restart development server

🔧 Temporary Workarounds

Disable development server

all

Stop using the vulnerable development server functionality

Stop any running react development servers

Network isolation

all

Restrict network access to development server

Configure firewall to block external access to port 3000

🧯 If You Can't Patch

  • Run development server on non-Windows operating system
  • Ensure development server only listens on localhost (127.0.0.1) and not all interfaces

🔍 How to Verify

Check if Vulnerable:

Check react-dev-utils version: npm list react-dev-utils | grep react-dev-utils

Check Version:

npm list react-dev-utils

Verify Fix Applied:

Verify version is >=1.0.4, >=2.0.2, >=3.1.2, >=4.2.2, or >=5.0.2 depending on major version

📡 Detection & Monitoring

Log Indicators:

  • Unusual process spawns from node.js
  • Editor launch commands with suspicious parameters
  • Network requests to development server from unexpected sources

Network Indicators:

  • External connections to development server port (default 3000)
  • Malformed HTTP requests to editor launch endpoint

SIEM Query:

process.name:node.exe AND process.cmdline:*editor* AND destination.port:3000

🔗 References

📤 Share & Export