dbcve.org
ClamavApplication

CVE-2024-20328

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-01
Fix available
A fix is available. Upgrade to 1.0.5 / 1.2.2 or later.
See remediation →
55/100
Remediation priority · Elevated
High EPSS Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability in ClamAV's VirusEvent feature allows local attackers to execute arbitrary commands by supplying file names containing command-line sequences. The feature unsafely handles file names during processing, enabling command execution with the privileges of the application service account.

MitigationApply the ClamAV software updates released to address this vulnerability, as no workarounds are available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ClamavApplication
Affected:>= 1.0.0, < 1.0.5>= 1.2.0, < 1.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed ClamAV version
    Run 'clamd --version' or check package manager (dpkg -l clamav, rpm -qi clamav)
    Affected if Version is >= 1.0.0 and < 1.0.5, or >= 1.2.0 and < 1.2.2
  2. Locate the ClamAV configuration file
    Find clamd.conf, typically in /etc/clamd.conf, /etc/clamd.d/, or the conf.d directory
    Affected if Configuration file exists and VirusEvent is present
  3. Check if VirusEvent feature is enabled
    Search for 'VirusEvent' directive in clamd.conf using 'grep -i virusevent /path/to/clamd.conf'
    Affected if VirusEvent directive is present and configured with a command
  4. Inspect the VirusEvent command configuration
    Read the VirusEvent line to see what command is configured for event handling
    Affected if VirusEvent points to a script or command that processes file names without sanitization
  5. Verify ClamAV service is running with VirusEvent configured
    Check if clamd/clamav-daemon service is active and the configuration contains a VirusEvent command
    Affected if ClamAV daemon runs with VirusEvent enabled in the configuration

You are affected if ClamAV version is 1.0.0 through 1.0.4, or 1.2.0 through 1.2.1, AND the VirusEvent feature is enabled in your clamd.conf configuration file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.5 / 1.2.2 or later
Fixed in 1.0.51.2.2
Interim mitigation

Apply the ClamAV software updates released to address this vulnerability, as no workarounds are available.

Recommended fix High confidence

ClamAV 1.0.5 or later (for 1.0.x branch); ClamAV 1.2.2 or later (for 1.2.x branch)

  1. 1. Identify the currently installed ClamAV version using 'clamdscan --version' or 'clamscan --version'
  2. 2. Determine which version branch your current installation falls into (1.0.x or 1.2.x)
  3. 3. For ClamAV versions >= 1.0.0 and < 1.0.5: upgrade to version 1.0.5 or later
  4. 4. For ClamAV versions >= 1.2.0 and < 1.2.2: upgrade to version 1.2.2 or later
  5. 5. Update the package using your system's package manager (e.g., 'apt-get update && apt-get upgrade clamav' for Debian/Ubuntu, or 'yum update clamav' for RHEL/CentOS)
  6. 6. Verify the new version is installed: 'clamdscan --version' or 'clamscan --version'
  7. 7. Ensure the VirusEvent configuration in clamd.conf is reviewed and secured after upgrade
Caveat Security update with no expected breaking changes; standard version upgrade within same major.minor series

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Clamav Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,370
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-20328 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data