Cyber Resilience

CVE-2024-20380

Clamav 1.3.0

Published
18 April 2024
Modified
23 July 2025
Patch / advisory
View advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.011 63th percentile
Risk Priority 60 floored blend · peak EPSS

Summary

CVE-2024-20380 is a high-severity Undefined Behavior for Input to API (CWE-475) vulnerability in Clamav Clamav. Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 37% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A vulnerability in the HTML parser of ClamAV could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability is due to an issue in the C to Rust foreign function…

more

interface. An attacker could exploit this vulnerability by submitting a crafted file containing HTML content to be scanned by ClamAV on an affected device. An exploit could allow the attacker to cause the ClamAV scanning process to terminate, resulting in a DoS condition on the affected software.

CWE(s)
CWE-475

Related Threats

CVEs Like This One

CVE-2024-20505Same product: Clamav Clamav
CVE-2024-20506Same product: Clamav Clamav
CVE-2024-20328Same product: Clamav Clamav
CVE-2025-20260Same product: Clamav Clamav
CVE-2026-20215Same product: Clamav Clamav
CVE-2026-20243Same product: Clamav Clamav
CVE-2026-20213Same product: Clamav Clamav
CVE-2026-20214Same product: Clamav Clamav
CVE-2026-20216Same product: Clamav Clamav
CVE-2026-20217Same product: Clamav Clamav

Affected Assets

clamav
clamav
1.3.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover calls that supply invalid control-parameter values before deployment.

SI-10 Information Input Validation good match

Validating inputs to API control parameters ensures only permitted values are supplied, structurally eliminating the source of undefined behavior.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices (coding standards, reviews, testing) directly prevent undefined behavior from invalid API inputs.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record this class of API-related weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect undefined behavior from invalid API inputs before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes API specification and validation that can prevent undefined behavior from invalid inputs.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate explicit input validation and defined behavior for API parameters.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles can require defensive coding that eliminates undefined behavior in APIs.

A.8.28 Secure coding partial match
prevents

Secure coding directly addresses avoiding undefined behavior by enforcing defined inputs and error handling in APIs.

References