{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-20506 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2024-20506 is a medium-severity vulnerability in Clamav Clamav, published on 4 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-20506 and fix it if it is affected.\n\nWhat it is: CVE-2024-20506 is a medium-severity vulnerability in Clamav Clamav, published on 4 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-20506 in the wild and no public exploit code.\n\nAffected product: Clamav Clamav. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-20506/ (Markdown: https://insights.sbomify.com/CVE-2024-20506/index.md)","id":"CVE-2024-20506","markdown":"https://insights.sbomify.com/CVE-2024-20506/index.md","name":"CVE-2024-20506","record":{"aliases":["AZL-48624","AZL-48665","DEBIAN-CVE-2024-20506","GHSA-h5fr-q576-q7rv","UBUNTU-CVE-2024-20506"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ClamAV antivirus","requires_auth":"low_privilege","summary":"A local authenticated attacker can corrupt critical system files by exploiting a symlink vulnerability in ClamAV's log handling, leading to privilege escalation.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"clamav","vendor":"clamav"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"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.\r\n\r\nThe 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ClamAV Privilege Handling Escalation Vulnerability","id":"CVE-2024-20506","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"clamav:clamav","products":["clamav:clamav"],"type":"privilege_escalation","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Cisco Meeting Management Information Disclosure Vulnerability","id":"CVE-2024-20507"},"packages":[],"prev":{"headline":"ClamAV Memory Handling DoS","id":"CVE-2024-20505"},"products":["ClamAV"],"published":"2024-09-04","related":[{"cvss_score":10,"headline":"Security feature bypass in n/a","id":"CVE-2010-0098","kev_date_added":null,"published":"2010-04-08"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2009-1372","kev_date_added":null,"published":"2009-04-23"},{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-2008-3914","kev_date_added":null,"published":"2008-09-09"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-0728","kev_date_added":null,"published":"2008-02-12"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2006-1615","kev_date_added":null,"published":"2006-04-06"},{"cvss_score":9.8,"headline":"ClamAV PDF Scanning Buffer Overflow Vulnerability","id":"CVE-2025-20260","kev_date_added":null,"published":"2025-06-18"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2013-7087","kev_date_added":null,"published":"2019-11-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-03","vendors":["Cisco"]},"summary":"A local authenticated attacker can corrupt critical system files by exploiting a symlink vulnerability in ClamAV's log handling, leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2024-20506/"}