First published: Thu Apr 06 2006(Updated: )
Multiple format string vulnerabilities in the logging code in Clam AntiVirus (ClamAV) before 0.88.1 might allow remote attackers to execute arbitrary code. NOTE: as of 20060410, it is unclear whether this is a vulnerability, as there is some evidence that the arguments are actually being sanitized properly.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
ClamAV | =0.86.2 | |
ClamAV | =0.02 | |
ClamAV | =0.8-rc3 | |
ClamAV | =0.15 | |
ClamAV | =0.75.1 | |
ClamAV | =0.65 | |
ClamAV | =0.81 | |
ClamAV | =0.86 | |
ClamAV | =0.01 | |
ClamAV | =0.85 | |
ClamAV | =0.84 | |
ClamAV | =0.3 | |
ClamAV | =0.70-rc | |
ClamAV | =0.86-rc1 | |
ClamAV | =0.68.1 | |
ClamAV | =0.03 | |
ClamAV | =0.87.1 | |
ClamAV | =0.74 | |
ClamAV | =0.86.1 | |
ClamAV | =0.71 | |
ClamAV | =0.60p | |
ClamAV | =0.80-rc | |
ClamAV | =0.85.1 | |
ClamAV | =0.13 | |
ClamAV | =0.81-rc1 | |
ClamAV | =0.10 | |
ClamAV | =0.80-rc3 | |
ClamAV | =0.12 | |
ClamAV | =0.23 | |
ClamAV | =0.84-rc1 | |
ClamAV | =0.80-rc2 | |
ClamAV | =0.80-rc1 | |
ClamAV | =0.60 | |
ClamAV | =0.83 | |
ClamAV | =0.20 | |
ClamAV | =0.80-rc4 | |
ClamAV | =0.70 | |
ClamAV | =0.14 | |
ClamAV | =0.24 | |
ClamAV | =0.66 | |
ClamAV | =0.51 | |
ClamAV | =0.52 | |
ClamAV | =0.22 | |
ClamAV | =0.72 | |
ClamAV | =0.75 | |
ClamAV | =0.05 | |
ClamAV | =0.54 | |
ClamAV | =0.80 | |
ClamAV | =0.87 | |
ClamAV | =0.21 | |
ClamAV | =0.84-rc2 | |
ClamAV | =0.67-1 | |
ClamAV | =0.14-pre | |
ClamAV | =0.67 | |
ClamAV | =0.68 | |
ClamAV | =0.53 | |
ClamAV | <=0.88 | |
ClamAV | =0.82 | |
ClamAV | =0.73 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2006-1615 is considered a high severity vulnerability due to potential remote code execution.
To fix CVE-2006-1615, users should upgrade to ClamAV version 0.88.1 or later.
CVE-2006-1615 affects multiple versions of ClamAV prior to 0.88.1, including versions like 0.86.2 and earlier.
Yes, CVE-2006-1615 could potentially allow remote attackers to execute arbitrary code due to format string vulnerabilities.
As of the last update, there is some evidence suggesting that argument sanitization may mitigate the impact of CVE-2006-1615.