CVE-2024-20328: Cisco ClamAV · OS Command Injection
Affects Cisco ClamAVSource CVE Database V5
Not known to be exploited · 84% EPSS · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 84.8% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 1 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Cisco ClamAV | Affected
| Fixed in– |
AI-suggested
European organizations should immediately identify all systems running ClamAV versions 1.2.0 or 1.2.1 and prioritize updating to the latest patched versions released by Cisco. Since no workarounds exist, patching is the only effective mitigation. Additionally, organizations should restrict local access to systems running ClamAV to trusted personnel only and enforce the principle of least privilege to minimize the impact of potential exploitation. Monitoring and alerting on unusual command executions or process behaviors related to ClamAV can help detect exploitation attempts. Regularly auditing VirusEvent configurations to ensure they follow security best practices is recommended. Implementing endpoint detection and response (EDR) solutions can further help identify suspicious activities stemming from this vulnerability. Finally, educating system administrators about the risks and ensuring timely patch management processes are critical to reducing exposure.
Description
A vulnerability in the VirusEvent feature of ClamAV could allow a local attacker to inject arbitrary commands with the privileges of the application service account.The vulnerability is due to unsafe handling of file names. A local attacker could exploit this vulnerability by supplying a file name containing command-line sequences. When processed on a system using configuration options for the VirusEvent feature, the attacker could cause the application to execute arbitrary commands. ClamAV has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.