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

Q: How do I fix CVE-2020-7613?

clamscan: upgrade to newer than 1.2.0. Exact commands for each OS are on this page.

Q: Is CVE-2020-7613 being exploited?

CVE-2020-7613 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-7613 affect?

CVE-2020-7613 affects clamscan. Severity is high (CVSS 8.1). 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-requisit

Q: How urgent is CVE-2020-7613?

Priority 59/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 8.1REMOTEUPGRADE

CVE-2020-7613 is a high-severity flaw (CVSS 8.1) affecting clamscan. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	2.1% (top 18%)
CISA exploited list	No
Weakness	CWE-78
Published	2020-04-07
Last modified	2026-06-17

Publisher (CNA): Snyk · Vendor: clamscan project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-04-07 14:15 UTCPublished CVE record published
2026-06-17 03:25 UTCUpdated Record last modified

clamscan project clamscan UPGRADE

Affected: <= 1.2.0

Fixed in: newer than 1.2.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy clamscan || rpm -q clamscan || clamscan --version

2. UPGRADE to newer than 1.2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade clamscan

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade clamscan

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-7613?

clamscan: upgrade to newer than 1.2.0. Exact commands for each OS are on this page.

Is CVE-2020-7613 being exploited?

CVE-2020-7613 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-7613 affect?

CVE-2020-7613 affects clamscan. Severity is high (CVSS 8.1). 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-requisit

How urgent is CVE-2020-7613?

Priority 59/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs