CVE-2006-1630: Medium severity clam anti-virus clamav vulnerability
Published Apr 6, 2006
·Updated
The clibitsetset function in libclamav/others.c in Clam AntiVirus (ClamAV) before 0.88.1 allows remote attackers to cause a denial of service via unspecified vectors that trigger an "invalid memory access."
Affected Software
30 affected components
Clam Anti-Virus clamav=0.84
Clam Anti-Virus clamav=0.80
Clam Anti-Virus clamav=0.84_rc1
Clam Anti-Virus clamav=0.80_rc3
Clam Anti-Virus clamav=0.80_rc4
Clam Anti-Virus clamav=0.65
Clam Anti-Virus clamav=0.68
Clam Anti-Virus clamav=0.86.1
Clam Anti-Virus clamav=0.82
Clam Anti-Virus clamav=0.85.1
Clam Anti-Virus clamav=0.87
Clam Anti-Virus clamav=0.85
Clam Anti-Virus clamav=0.80_rc1
Clam Anti-Virus clamav=0.75.1
Clam Anti-Virus clamav=0.86.2
Clam Anti-Virus clamav=0.67
Clam Anti-Virus clamav=0.81
Clam Anti-Virus clamav=0.54
Clam Anti-Virus clamav=0.53
Clam Anti-Virus clamav=0.70
Clam Anti-Virus clamav=0.80_rc2
Clam Anti-Virus clamav=0.60
Clam Anti-Virus clamav=0.86
Clam Anti-Virus clamav=0.83
Clam Anti-Virus clamav=0.68.1
Clam Anti-Virus clamav=0.88
Clam Anti-Virus clamav=0.87.1
Clam Anti-Virus clamav=0.84_rc2
Clam Anti-Virus clamav=0.51
Clam Anti-Virus clamav=0.52
Remediation
Patch Available
Patch Available
Patch Available
Event History
Apr 6, 2006
CVE Published
10:04 PM
Apr 7, 2006
CVE Published
via MITRE·02:00 AM
Data Sourced
via MITRE·02:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2006-1630?
CVE-2006-1630 is classified as a denial of service vulnerability that can be exploited by remote attackers.
2
How do I fix CVE-2006-1630?
To fix CVE-2006-1630, upgrade Clam AntiVirus to version 0.88.1 or later.
3
Which versions of ClamAV are affected by CVE-2006-1630?
CVE-2006-1630 affects multiple versions of ClamAV, including 0.84, 0.80, and various release candidates leading up to 0.88.
4
What happens if CVE-2006-1630 is exploited?
If exploited, CVE-2006-1630 can lead to an invalid memory access, causing the ClamAV service to crash.
5
Is there a known workaround for CVE-2006-1630?
There are no known workarounds for CVE-2006-1630; the best practice is to upgrade the software.