Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-20506ClamAV Privilege Handling Escalation Vulnerability

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.

Timeline

  1. ID reserved

    By cisco

  2. · 10 months later

    Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-20506, by who scored it
Scored byCVSSScoreVector
ciscoCNA (assigner)3.1Medium6.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
NVDNVD · Modified3.1Medium6.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
EPSS (exploitation in 30 days)
0.32% · top 75% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.1.

Affected products

  • Cisco · ClamAV

    • affected 1.4.0
    • affected 1.3.2
    • affected 1.0.6
    • affected 1.0.5
    • affected 1.0.4
    • affected 1.0.3
    • affected 1.0.2
    • affected 1.0.1
    • affected 1.0.0
    • affected 1.2.x
    • affected 0.105.x
    • affected 0.104.x
    • affected 0.103.11
    • affected 0.103.10
    • affected 0.103.9
    • affected 0.103.8
    • affected 0.103.7
    • affected 0.103.6
    • affected 0.103.5
    • affected 0.103.4
    • affected 0.103.3
    • affected 0.103.2
    • affected 0.103.1
    • affected 0.103.0

References

References2

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-20506 badge
[![CVE-2024-20506](https://cveledger.app/badge/CVE-2024-20506.svg)](https://cveledger.app/cve/CVE-2024-20506)

Record last updated .