7.5 CVE-2026-20345

Enriched by CISA
 

A vulnerability in the GPT file format parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition or possibly other expanded impacts as a result of memory corruption on an affected device. This vulnerability is due to improper handling of an endian conversion operation, which may result in an out-of-bounds buffer write. An attacker could exploit this vulnerability by submitting a crafted GPT file to be scanned by ClamAV on an affected device. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate, resulting in a DoS condition on the affected software.
https://nvd.nist.gov/vuln/detail/CVE-2026-20345

Categories

CWE-121 : Stack-based Buffer Overflow
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). "Stack Overflow" is often used to mean the same thing as stack-based buffer overflow, however it is also used on occasion to mean stack exhaustion, usually a result from an excessively recursive function call. Due to the ambiguity of the term, use of stack overflow to describe either circumstance is discouraged. Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues. Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.) Use tools that are integrated duringcompilation to insert runtime error-checking mechanismsrelated to memory safety errors, such as AddressSanitizer(ASan) for C/C++ [REF-1518]. Use an abstraction library to abstract away risky APIs. Not a complete solution. Implement and perform bounds checking on input. Do not use dangerous functions such as gets. Use safer, equivalent functions which check for boundary errors. Stack-based buffer overflows in SFK for wifi chipset used for IoT/embedded devices, as exploited in the wild per CISA KEV.

References


 

AFFECTED (from MITRE)

Vendor Product Versions
Cisco Cisco Secure Endpoint
  • 1.12.3 [affected]
  • 1.8.0 [affected]
  • 1.11.1 [affected]
  • 1.12.4 [affected]
  • 1.10.0 [affected]
  • 1.12.0 [affected]
  • 1.8.1 [affected]
  • 1.10.1 [affected]
  • 1.10.2 [affected]
  • 1.12.2 [affected]
  • 1.6.0 [affected]
  • 1.9.0 [affected]
  • 1.7.0 [affected]
  • 1.12.1 [affected]
  • 1.12.6 [affected]
  • 1.8.4 [affected]
  • 1.11.0 [affected]
  • 1.9.1 [affected]
  • 1.12.5 [affected]
  • 2.0.2 [affected]
  • 1.1.0 [affected]
  • 1.14.0 [affected]
  • 2.4.0 [affected]
  • 1.15.2 [affected]
  • 1.16.0 [affected]
  • 1.21.0 [affected]
  • 1.22.2 [affected]
  • 1.24.5 [affected]
  • 1.19.0 [affected]
© 2022 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.

CPE

cpe start end

REMEDIATION


EXPLOITS

Exploit-db.com

id description date
No known exploits

POC Github

Url
No known exploits

Other Nist (github, ...)

Url
No known exploits

CAPEC

Common Attack Pattern Enumerations and Classifications

id description severity
No entry