CVE-2024-20328

CRITICALNVD 5.39.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 85% probability of exploitation within the next 30 days (top 0.3% of all CVEs). NVD baseline CVSS 5.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 85%
CISA-KEV: Not listedEPSS PROB: 85%CVSS: 5.3Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.3
EG Score
9.0(high)
EG Risk
74(Track)
EG Risk 74/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation85% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
85%
EPSS %ILE
100%
KEV
Not listed

Published

March 1, 2024

Last Modified

November 4, 2025

References (3)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibclamav11 (1.0.5+dfsg-0ubuntu0.23.10.1) @ mantic2026-05-24ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 17× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-26 14:53 UTCEPSS rescore
  2. 2026-07-24 14:16 UTCEPSS rescore
  3. 2026-07-23 14:17 UTCEPSS rescore
  4. 2026-07-23 14:17 UTCEPSS rescore
  5. 2026-07-23 02:33 UTCEG score recompute▲ 3.70
  6. 2026-07-22 23:19 UTCEG score recompute
  7. 2026-07-22 14:07 UTCEPSS rescore
  8. 2026-07-20 17:06 UTCEPSS rescore
  9. 2026-07-15 16:56 UTCEPSS rescore
  10. 2026-07-15 16:56 UTCEPSS rescore
  11. 2026-07-14 18:10 UTCOSV refresh
  12. 2026-07-13 06:11 UTCEPSS rescore
  13. 2026-07-13 06:11 UTCEPSS rescore
  14. 2026-07-11 08:26 UTCEPSS rescore
  15. 2026-07-05 02:29 UTCEPSS rescore
  16. 2026-06-28 04:55 UTCEPSS rescore
  17. 2026-06-28 04:55 UTCEPSS rescore
  18. 2026-06-26 19:07 UTCOSV refresh
  19. 2026-06-25 13:48 UTCEPSS rescore
  20. 2026-06-25 13:48 UTCEPSS rescore
  21. 2026-06-23 21:32 UTCEPSS rescore
  22. 2026-06-23 21:32 UTCEPSS rescore
  23. 2026-06-17 17:52 UTCEPSS rescore
  24. 2026-06-17 17:51 UTCEPSS rescore
  25. 2026-06-16 17:51 UTCEPSS rescore
Show 48 more
  1. 2026-06-16 17:51 UTCEPSS rescore
  2. 2026-06-15 17:47 UTCEPSS rescore
  3. 2026-06-14 23:16 UTCEPSS rescore
  4. 2026-06-13 22:59 UTCEPSS rescore
  5. 2026-06-13 22:59 UTCEPSS rescore
  6. 2026-06-12 23:11 UTCEPSS rescore
  7. 2026-06-12 23:11 UTCEPSS rescore
  8. 2026-06-11 13:59 UTCEPSS rescore
  9. 2026-06-11 13:59 UTCEPSS rescore
  10. 2026-06-10 22:17 UTCEPSS rescore
  11. 2026-06-10 22:17 UTCEPSS rescore
  12. 2026-06-10 13:21 UTCEPSS rescore
  13. 2026-06-10 13:21 UTCEPSS rescore
  14. 2026-06-09 03:30 UTCOSV refresh
  15. 2026-06-08 14:16 UTCEPSS rescore
  16. 2026-06-08 14:16 UTCEPSS rescore
  17. 2026-06-07 15:24 UTCEPSS rescore
  18. 2026-06-07 15:24 UTCEPSS rescore
  19. 2026-06-06 13:46 UTCEPSS rescore
  20. 2026-06-06 13:46 UTCEPSS rescore
  21. 2026-06-05 22:46 UTCEPSS rescore
  22. 2026-06-05 22:46 UTCEPSS rescore
  23. 2026-06-05 06:09 UTCEPSS rescore
  24. 2026-06-05 06:09 UTCEPSS rescore
  25. 2026-06-04 13:11 UTCEPSS rescore
  26. 2026-06-04 13:11 UTCEPSS rescore
  27. 2026-06-04 13:11 UTCEPSS rescore
  28. 2026-06-02 20:12 UTCEPSS rescore
  29. 2026-06-02 20:12 UTCEPSS rescore
  30. 2026-06-01 13:51 UTCEPSS rescore
  31. 2026-06-01 13:51 UTCEPSS rescore
  32. 2026-05-31 22:30 UTCEPSS rescore
  33. 2026-05-31 22:30 UTCEPSS rescore
  34. 2026-05-31 00:15 UTCEPSS rescore
  35. 2026-05-31 00:15 UTCEPSS rescore
  36. 2026-05-29 13:43 UTCEPSS rescore
  37. 2026-05-28 13:44 UTCEPSS rescore
  38. 2026-05-28 13:44 UTCEPSS rescore
  39. 2026-05-28 13:44 UTCEPSS rescore
  40. 2026-05-27 13:40 UTCEPSS rescore
  41. 2026-05-26 13:43 UTCEPSS rescore
  42. 2026-05-26 13:43 UTCEPSS rescore
  43. 2026-05-26 07:18 UTCEPSS rescore
  44. 2026-05-26 07:18 UTCEPSS rescore
  45. 2026-05-26 07:18 UTCEPSS rescore
  46. 2026-05-24 07:26 UTCEG score recompute
  47. 2026-05-24 07:26 UTCVendor advisory
  48. 2026-05-24 07:26 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2024-20328?
CVE-2024-20328 is a critical vulnerability published on March 1, 2024. 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…
When was CVE-2024-20328 disclosed?
CVE-2024-20328 was first published in the National Vulnerability Database on March 1, 2024, with the most recent update on November 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-20328 actively exploited?
CVE-2024-20328 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85% probability of exploitation in the next 30 days, which ranks it in the top 0.3% of all scored CVEs.
What is the CVSS score of CVE-2024-20328?
CVE-2024-20328 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2024-20328?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-20328, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-20328

Explore →

Is Your Infrastructure Affected by CVE-2024-20328?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs