CVE-2019-15961
📋 TL;DR
This vulnerability in ClamAV allows remote attackers to cause denial of service by sending specially crafted email files that trigger inefficient MIME parsing, resulting in extremely long scan times. Systems running ClamAV versions 0.102.0, 0.101.4 and prior are affected when processing email files through the vulnerable parsing module.
💻 Affected Systems
- Clam AntiVirus (ClamAV)
📦 What is this software?
Clamav by Clamav
Clamav by Clamav
Email Security Appliance Firmware by Cisco
Email Security Appliance Firmware by Cisco
Ubuntu Linux by Canonical
Ubuntu Linux by Canonical
⚠️ Risk & Real-World Impact
Worst Case
Complete denial of service where ClamAV scanning processes become unresponsive indefinitely, blocking all email scanning and potentially affecting dependent services.
Likely Case
Degraded performance and temporary service disruption as scanning processes consume excessive resources on affected systems.
If Mitigated
Minimal impact with proper network filtering and updated ClamAV versions preventing exploitation.
🎯 Exploit Status
Exploitation requires sending a crafted email file to trigger the inefficient parsing. No authentication needed.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 0.102.1, 0.101.5
Vendor Advisory: https://bugzilla.clamav.net/show_bug.cgi?id=12380
Restart Required: Yes
Instructions:
1. Update ClamAV to version 0.102.1 or 0.101.5 or later. 2. Stop ClamAV services. 3. Install updated packages from your distribution's repository. 4. Restart ClamAV services. 5. Verify the update was successful.
🔧 Temporary Workarounds
Disable email scanning
allTemporarily disable ClamAV's email parsing functionality if not required
Edit clamd.conf and set ScanMail to no
Restart clamd service
Rate limit email processing
allImplement rate limiting on email processing to mitigate DoS impact
Configure mail server to limit concurrent scans
Set MaxScanSize in clamd.conf
🧯 If You Can't Patch
- Implement network filtering to block suspicious email attachments before they reach ClamAV
- Monitor ClamAV process resource usage and implement automated restart thresholds
🔍 How to Verify
Check if Vulnerable:
Run 'clamscan --version' and check if version is 0.102.0, 0.101.4 or earlier
Check Version:
clamscan --version | head -1
Verify Fix Applied:
Confirm version is 0.102.1, 0.101.5 or later using 'clamscan --version'
📡 Detection & Monitoring
Log Indicators:
- Extended scan times for email files in ClamAV logs
- High CPU usage by clamd processes
- Process timeouts or crashes
Network Indicators:
- Unusually large email attachments with specific MIME structures
- Email files causing prolonged scanning
SIEM Query:
source="clamav" AND ("scan time" > 300 OR "timeout" OR "denial of service")
🔗 References
- https://bugzilla.clamav.net/show_bug.cgi?id=12380
- https://lists.debian.org/debian-lts-announce/2020/02/msg00016.html
- https://quickview.cloudapps.cisco.com/quickview/bug/CSCvr56010
- https://security.gentoo.org/glsa/202003-46
- https://usn.ubuntu.com/4230-2/
- https://bugzilla.clamav.net/show_bug.cgi?id=12380
- https://lists.debian.org/debian-lts-announce/2020/02/msg00016.html
- https://quickview.cloudapps.cisco.com/quickview/bug/CSCvr56010
- https://security.gentoo.org/glsa/202003-46
- https://usn.ubuntu.com/4230-2/