Skip to main content
CVE-2024-20506VulnerabilityPublished Updated

CVE-2024-20506: Cisco ClamAV · Unchecked Error Condition

Affects Cisco ClamAVSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium · fixed in 1.3.0 : update Cisco ClamAV when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.3.0, 0.106.0, 0.105.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

Upgrade Cisco ClamAV to 1.3.0, 0.106.0 or 0.105.0.

Affected software

ProductAffectedFixed in
Cisco ClamAVAffected
  • =1.4.0
  • =1.3.2
  • =1.0.6
  • =1.0.5
  • =1.0.4
  • =1.0.3
  • =1.0.2
  • =1.0.1
  • =1.0.0
  • >=1.2.0 <1.3.0
  • >=0.105.0 <0.106.0
  • >=0.104.0 <0.105.0
  • =0.103.11
  • =0.103.10
  • =0.103.9
  • =0.103.8
  • =0.103.7
  • =0.103.6
  • =0.103.5
  • =0.103.4
  • =0.103.3
  • =0.103.2
  • =0.103.1
  • =0.103.0
Fixed in
  • 1.3.0
  • 0.106.0
  • 0.105.0

AI-suggested

1. Upgrade ClamAV to the latest available version where this vulnerability is patched. 2. Restrict local user privileges to prevent unauthorized modification of ClamD log files and control who can restart the ClamD service. 3. Implement file integrity monitoring on ClamD log files and critical system files to detect unauthorized symbolic link creation or file tampering. 4. Harden system permissions to prevent symbolic link attacks, including disabling symlink following in sensitive directories if possible. 5. Use process supervision tools that prevent unauthorized restarts of ClamD or require administrative approval. 6. Conduct regular audits of local user accounts and privileges to minimize insider threat risks. 7. Employ endpoint detection and response (EDR) solutions to detect suspicious local activity related to ClamD. 8. Develop incident response plans that include recovery procedures for corrupted system files to minimize downtime.

Description

A vulnerability in the ClamD service module of Clam AntiVirus (ClamAV) versions 1.4.0, 1.3.2 and prior versions, all 1.2.x versions, 1.0.6 and prior versions, all 0.105.x versions, all 0.104.x versions, and 0.103.11 and all prior versions could allow an authenticated, local attacker to corrupt critical system files. The vulnerability is due to allowing the ClamD process to write to its log file while privileged without checking if the logfile has been replaced with a symbolic link. An attacker could exploit this vulnerability if they replace the ClamD log file with a symlink to a critical system file and then find a way to restart the ClamD process. An exploit could allow the attacker to corrupt a critical system file by appending ClamD log messages after restart.

References

Community reviews

Loading reviews…