blob: 299013480f3e7b69db019fd0609ea354858419d4 [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200909-04">
<title>Clam AntiVirus: Multiple vulnerabilities</title>
Multiple vulnerabilities in ClamAV allow for the remote execution of
arbitrary code or Denial of Service.
<product type="ebuild">clamav</product>
<announced>September 09, 2009</announced>
<revised>September 09, 2009: 01</revised>
<package name="app-antivirus/clamav" auto="yes" arch="*">
<unaffected range="ge">0.95.2</unaffected>
<vulnerable range="lt">0.95.2</vulnerable>
Clam AntiVirus (short: ClamAV) is an anti-virus toolkit for UNIX,
designed especially for e-mail scanning on mail gateways.
Multiple vulnerabilities have been found in ClamAV:
vendor reported a Divide-by-zero error in the PE ("Portable
Executable"; Windows .exe) file handling of ClamAV
<li>Jeffrey Thomas Peckham found a flaw in
libclamav/untar.c, possibly resulting in an infinite loop when
processing TAR archives in clamd and clamscan (CVE-2009-1270).</li>
<li>Martin Olsen reported a vulnerability in the CLI_ISCONTAINED macro
in libclamav/others.h, when processing UPack archives
<li>Nigel disclosed a stack-based buffer overflow
in the "cli_url_canon()" function in libclamav/phishcheck.c when
processing URLs (CVE-2009-1372).</li>
<impact type="normal">
A remote attacker could entice a user or automated system to process a
specially crafted UPack archive or a file containing a specially
crafted URL, possibly resulting in the remote execution of arbitrary
code with the privileges of the user running the application, or a
Denial of Service. Furthermore, a remote attacker could cause a Denial
of Service by supplying a specially crafted TAR archive or PE
executable to a Clam AntiVirus instance.
There is no known workaround at this time.
All Clam AntiVirus users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=app-antivirus/clamav-0.95.2&quot;</code>
<uri link="">CVE-2008-6680</uri>
<uri link="">CVE-2009-1270</uri>
<uri link="">CVE-2009-1371</uri>
<uri link="">CVE-2009-1372</uri>
<metadata tag="requester" timestamp="Mon, 01 Jun 2009 22:30:28 +0000">
<metadata tag="submitter" timestamp="Fri, 28 Aug 2009 09:13:38 +0000">
<metadata tag="bugReady" timestamp="Mon, 31 Aug 2009 03:38:38 +0000">