Vulnerability in clamscan (CVE-2020-7613)
Summary
Vulnerability in clamscan (CVE-2020-7613). Successful exploitation can lead to full system takeover. Exploitable via _is_clamav_binary. Mitigation: upgrade to 1.3.0 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-7613 has been found in clamscan.
Attackers can target a specific entry point like _is_clamav_binary over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade clamscan to 1.3.0 or later.
If unsure, ask your IT team or search "clamscan CVE-2020-7613" on the vendor's site.
CVE-2020-7613 (clamscan) — CWE-74
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: _is_clamav_binary / Index.js
Patched: 1.3.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-74) exists in clamscan. Attackers reach the vulnerable code path via _is_clamav_binary without authentication.
Check the vendor advisory for the affected versions of clamscan. Attack surface: _is_clamav_binary / Index.js.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 1.3.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'clamscan' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'clamscan' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
clamscanを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade clamscan to 1.3.0ステージング環境で 1.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- report snyk.io
- web github.com
- web github.com
- web huntr.dev