{"answers":{"affected":"2 open source packages ship an affected version, including clamscan. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7613 in the wild and no public exploit code.","fix":"Upgrade clamscan to 1.3.0 or later.","what":"CVE-2020-7613 is a high-severity command injection vulnerability in clamscan, published on 7 Apr 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-7613 and fix it if it is affected.\n\nWhat it is: CVE-2020-7613 is a high-severity command injection vulnerability in clamscan, published on 7 Apr 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-7613 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- clamscan (npm): affected all versions; fixed in 1.3.0\n- clamscan (npm): affected all versions; fixed in 1.3.0\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-7613/ (Markdown: https://insights.sbomify.com/CVE-2020-7613/index.md)","id":"CVE-2020-7613","markdown":"https://insights.sbomify.com/CVE-2020-7613/index.md","name":"CVE-2020-7613","record":{"aliases":["GHSA-5v25-xr56-phph","SNYK-JS-CLAMSCAN-564113"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js ClamAV wrapper","requires_auth":"none","summary":"Attackers can execute arbitrary commands via the _is_clamav_binary function if a specific folder exists, affecting clamscan users.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"clamscan","vendor":"clamscan_project"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/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":"clamscan through 1.2.0 is vulnerable to Command Injection. It is possible to inject arbitrary commands as part of the `_is_clamav_binary` function located within `Index.js`. It should be noted that this vulnerability requires a pre-requisite that a folder should be created with the same command that will be chained to execute. This lowers the risk of this issue.","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":"Clamscan vulnerable to command injection","id":"CVE-2020-7613","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Command Injection in npm-programmatic","id":"CVE-2020-7614"},"packages":[{"ecosystem":"npm","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"clamscan","purl":null,"source":"GHSA-5v25-xr56-phph"},{"ecosystem":"npm","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"clamscan","purl":"pkg:npm/clamscan","source":"GHSA-5v25-xr56-phph"}],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2020-7612"},"products":["clamscan"],"published":"2020-04-07","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 the _is_clamav_binary function if a specific folder exists, affecting clamscan users.","url":"https://insights.sbomify.com/CVE-2020-7613/"}