Skip to content

← Public intelligence

npm package

react-dev-utils

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.6npmAmendedPublished

    react-dev-utils OS Command Injection in function getProcessForPort

    CVE-2021-24033 · GHSA-5q6m-3h65-w53x

    Affected
    • npm react-dev-utils >= 0.4.0, < 11.0.4
    Fixed in
    11.0.4· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 11.0.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. UnratednpmAmendedPublished

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

    CVE-2018-6342 · GHSA-29gp-92wp-94q8

    Affected
    • npm react-dev-utils >= 1.0.0, < 1.0.4; >= 2.0.0, < 2.0.2; >= 3.0.0, < 3.1.2; >= 4.0.0, < 4.2.2; >= 5.0.0, < 5.0.2
    Fixed in
    1.0.43.1.22.0.24.2.25.0.2· Vendor fix available
    Issue
    react-dev-utils on Windows is vulnerable to remote code execution. Recommendation 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

    Recommended action: Upgrade to 5.0.2, 4.2.2, 3.1.2 or 2 more by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →