{"answers":{"affected":"2 open source packages ship an affected version, including pulverizr. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7604 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-7604 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-7604 is a critical command injection vulnerability in pulverizr, 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-7604 and fix it if it is affected.\n\nWhat it is: CVE-2020-7604 is a critical command injection vulnerability in pulverizr, 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-7604 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pulverizr (npm): affected all versions up to 0.7.0; no fix listed\n- pulverizr (npm): affected all versions up to 0.7.0; 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-7604/ (Markdown: https://insights.sbomify.com/CVE-2020-7604/index.md)","id":"CVE-2020-7604","markdown":"https://insights.sbomify.com/CVE-2020-7604/index.md","name":"CVE-2020-7604","record":{"aliases":["GHSA-fmf5-j5j9-99pp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js job library","requires_auth":"none","summary":"Attackers can execute arbitrary commands via unsanitized filename input in the pulverizr library, requiring file creation for exploitation.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"pulverizr","vendor":"pulverizr_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":"pulverizr through 0.7.0 allows execution of arbitrary commands. Within \"lib/job.js\", the variable \"filename\" can be controlled by the attacker. This function uses the variable \"filename\" to construct the argument of the exec call without any sanitization. In order to successfully exploit this vulnerability, an attacker will need to create a new file with the same name as the attack command.","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 pulverizr","id":"CVE-2020-7604","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 gulp-tape","id":"CVE-2020-7605"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.7.0"],"package":"pulverizr","purl":null,"source":"GHSA-fmf5-j5j9-99pp"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.7.0"],"package":"pulverizr","purl":"pkg:npm/pulverizr","source":"GHSA-fmf5-j5j9-99pp"}],"prev":{"headline":"OS Command Injection in closure-compiler-stream","id":"CVE-2020-7603"},"products":["pulverizr"],"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 filename input in the pulverizr library, requiring file creation for exploitation.","url":"https://insights.sbomify.com/CVE-2020-7604/"}