{"answers":{"affected":"2 open source packages ship an affected version, including react-dev-utils. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-24033 in the wild and no public exploit code.","fix":"Upgrade react-dev-utils to 11.0.4 or later.","what":"CVE-2021-24033 is a medium-severity command injection vulnerability in Facebook react-dev-utils, published on 9 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-24033 and fix it if it is affected.\n\nWhat it is: CVE-2021-24033 is a medium-severity command injection vulnerability in Facebook react-dev-utils, published on 9 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-24033 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- react-dev-utils (npm): affected from 0.4.0; fixed in 11.0.4\n- react-dev-utils (npm): affected from 0.4.0; fixed in 11.0.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-24033/ (Markdown: https://insights.sbomify.com/CVE-2021-24033/index.md)","id":"CVE-2021-24033","markdown":"https://insights.sbomify.com/CVE-2021-24033/index.md","name":"CVE-2021-24033","record":{"aliases":["GHSA-5q6m-3h65-w53x"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"React dev utilities","requires_auth":"none","summary":"Attackers can execute arbitrary commands if custom code passes user input to the getProcessForPort function in react-dev-utils.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"facebook","cpe":[{"product":"react-dev-utils","vendor":"facebook"}],"cvss":{"score":5.6,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"react-dev-utils OS Command Injection in function `getProcessForPort`","id":"CVE-2021-24033","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Path traversal in WhatsApp Business for Android","id":"CVE-2021-24035"},"packages":[{"ecosystem":"npm","fixed":["11.0.4"],"introduced":["0.4.0"],"last_affected":[],"package":"react-dev-utils","purl":null,"source":"GHSA-5q6m-3h65-w53x"},{"ecosystem":"npm","fixed":["11.0.4"],"introduced":["0.4.0"],"last_affected":[],"package":"react-dev-utils","purl":"pkg:npm/react-dev-utils","source":"GHSA-5q6m-3h65-w53x"}],"prev":{"headline":"Information disclosure in Zstandard","id":"CVE-2021-24032"},"products":["react-dev-utils"],"published":"2021-03-09","related":[{"cvss_score":9.8,"headline":"react-dev-utils on Windows vulnerable to Remote Code Execution","id":"CVE-2018-6342","kev_date_added":null,"published":"2018-12-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["Facebook"]},"summary":"Attackers can execute arbitrary commands if custom code passes user input to the getProcessForPort function in react-dev-utils.","url":"https://insights.sbomify.com/CVE-2021-24033/"}