{"answers":{"affected":"2 open source packages ship an affected version, including closure-compiler-stream. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7603 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-7603 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-7603 is a critical command injection vulnerability in closure-compiler-stream, published on 15 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-7603 and fix it if it is affected.\n\nWhat it is: CVE-2020-7603 is a critical command injection vulnerability in closure-compiler-stream, published on 15 Mar 2020. 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-2020-7603 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- closure-compiler-stream (npm): affected all versions up to 0.1.15; no fix listed\n- closure-compiler-stream (npm): affected all versions up to 0.1.15; no fix listed\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-2020-7603/ (Markdown: https://insights.sbomify.com/CVE-2020-7603/index.md)","id":"CVE-2020-7603","markdown":"https://insights.sbomify.com/CVE-2020-7603/index.md","name":"CVE-2020-7603","record":{"aliases":["GHSA-m647-5wf9-3jp3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js compiler library","requires_auth":"none","summary":"Attackers can execute arbitrary commands via unsanitized options in the closure-compiler-stream npm library.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"closure-compiler-stream","vendor":"closure-compiler-stream_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"closure-compiler-stream through 0.1.15 allows execution of arbitrary commands. The argument \"options\" of the exports function in \"index.js\" can be controlled by users without any sanitization.","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":false,"headline":"OS Command Injection in closure-compiler-stream","id":"CVE-2020-7603","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2020"},"n_packages":2,"n_references":1,"next":{"headline":"OS Command Injection in pulverizr","id":"CVE-2020-7604"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.1.15"],"package":"closure-compiler-stream","purl":null,"source":"GHSA-m647-5wf9-3jp3"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.1.15"],"package":"closure-compiler-stream","purl":"pkg:npm/closure-compiler-stream","source":"GHSA-m647-5wf9-3jp3"}],"prev":{"headline":"OS Command Injection in node-prompt-here","id":"CVE-2020-7602"},"products":["closure-compiler-stream"],"published":"2020-03-15","related":[],"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-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands via unsanitized options in the closure-compiler-stream npm library.","url":"https://insights.sbomify.com/CVE-2020-7603/"}