CVE-2026-76416
HIGH(7.5)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CVSS 7.5 — Hoch
Erwähnungen (letzte 60 Tage)
EPSS-Score
0.5%
Exploit-Wahrscheinlichkeit (30 Tage)
CVSS Score
7.5
Technische Schwere
Beschreibung
A vulnerability in the InstallShield file parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to incomplete error checking when the InstallShield File Parser is performing a scan. An attacker could exploit this vulnerability by sending a crafted InstallShield file to be scanned. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate due to an infinite loop, resulting in a DoS condition on the affected software.
Erkennung & Indikatoren
Ausnutzung
In den geprüften Quellen nicht genannt
Behobene Versionen
- 1.29.3
- 1.27.5
- 8.6.4
Threat-Hunting-Queries
Detection for crafted InstallShield files causing an infinite loop in ClamAV. This query looks for repeated ClamAV process terminations or high CPU usage indicative of a denial-of-service condition.
Sentinel/Defender KQL
DeviceProcessEvents
| where FileName == "clamscan.exe" or FileName == "clamd.exe"
| summarize (TerminationCount, LastTerminationTime)=count() by DeviceId, InitiatingProcessFileName
| where TerminationCount > 5 // Adjust threshold as needed for your environment
| project DeviceId, InitiatingProcessFileName, TerminationCount, LastTerminationTime
| join kind=inner (DeviceProcessEvents
| where FileName == "clamscan.exe" or FileName == "clamd.exe"
| summarize (AvgCpuUsage, MaxCpuUsage)=avg(ProcessCpuCycles) by DeviceId, InitiatingProcessFileName
| where MaxCpuUsage > 90 // High CPU usage
) on DeviceId, InitiatingProcessFileNameSplunk SPL
(sourcetype="ms:defender:atp" OR sourcetype="syslog")
| where (process_name="clamscan.exe" OR process_name="clamd.exe")
| stats count as TerminationCount, latest(_time) as LastTerminationTime by host, process_name
| where TerminationCount > 5
| join host, process_name [search (sourcetype="ms:defender:atp" OR sourcetype="syslog")
| where (process_name="clamscan.exe" OR process_name="clamd.exe")
| stats avg(cpu_usage) as AvgCpuUsage, max(cpu_usage) as MaxCpuUsage by host, process_name
| where MaxCpuUsage > 90]
| table host, process_name, TerminationCount, LastTerminationTime, AvgCpuUsage, MaxCpuUsageSigma
title: ClamAV InstallShield DoS
id: 00000000-0000-0000-0000-000000000000 # Placeholder - generate a unique GUID
status: experimental
description: Detects potential denial-of-service conditions in ClamAV due to crafted InstallShield files, indicated by repeated process terminations or sustained high CPU usage.
author: SecBoard
date: 2026/11/18
logsource:
category: process_creation
product: windows
detection:
selection_termination:
Image|endswith:
- '\clamscan.exe'
- '\clamd.exe'
condition: selection_termination | count() > 5
timeframe: 5m
level: high
---
title: ClamAV InstallShield DoS - High CPU
id: 00000000-0000-0000-0000-000000000001 # Placeholder - generate a unique GUID
status: experimental
description: Detects potential denial-of-service conditions in ClamAV due to crafted InstallShield files, indicated by sustained high CPU usage.
author: SecBoard
date: 2026/11/18
logsource:
category: process_performance
product: windows
detection:
selection_cpu:
Image|endswith:
- '\clamscan.exe'
- '\clamd.exe'
CpuUsage|gte: 90
condition: selection_cpu | count() > 3 # Sustained high CPU over multiple samples
timeframe: 5m
level: highElastic ES|QL
from process where process.name in ("clamscan.exe", "clamd.exe")
| stats termination_count = count() by host.name, process.name
| where termination_count > 5
| join {
from process where process.name in ("clamscan.exe", "clamd.exe")
| stats avg_cpu_usage = avg(process.cpu.usage), max_cpu_usage = max(process.cpu.usage) by host.name, process.name
| where max_cpu_usage > 90
} on host.name, process.name
| select host.name, process.name, termination_count, avg_cpu_usage, max_cpu_usageSecBoard-generated · behavioral · requires customization — Von SecBoard erzeugt und nicht in einer Zielumgebung validiert. Vor dem Einsatz an die eigene Protokollierung anpassen.