CVE-2024-20328
5.3 · MEDIUMOverview
CVE-2024-20328 is a medium-severity vulnerability affecting clamav clamav. It was published on March 1, 2024 and has a CVSS 3.1 base score of 5.3 (MEDIUM).
This vulnerability has a CVSS 3.1 base score of 5.3, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.
Technical 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.
Remediation
Check the references section for vendor advisories and patches from clamav. Update clamav to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| clamav | clamav | >= 1.0.0, < 1.0.5 | Affected |
Frequently Asked Questions
What is CVE-2024-20328?
CVE-2024-20328 is a medium-severity vulnerability affecting clamav clamav. It was published on March 1, 2024 and has a CVSS 3.1 base score of 5.3 (MEDIUM).
How severe is CVE-2024-20328?
This vulnerability has a CVSS 3.1 base score of 5.3, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.
How do I fix or remediate CVE-2024-20328?
Check the references section for vendor advisories and patches from clamav. Update clamav to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2024-20328?
CyberStrike's AI-powered security agents can automatically detect CVE-2024-20328 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related MEDIUM CVEs from 2024
View all →OCSInventory allow stored email template with special characters that lead to a Stored cross-site Sc
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation
This vulnerability exist in Skyworth Router CM5100, version 4.1.1.24, due to insufficient validation