Clamav was updated to version 0.88.1 to fix the following security Clamav was updated to version 0.88.1 to fix the following security problems: problems: - An integer overflow in the PE header parser (CVE-2006-1614). - Format string bugs in the logging code could potentially beexploited to execute arbitrary code (CVE-2006-1615).. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: clamav Announcement ID: SUSE-SA:2006:020 Date: Tue, 11 Apr 2006 15:00:00 +0000 Affected Products: SUSE LINUX 10.0 SUSE LINUX 9.3 SUSE LINUX 9.2 SUSE LINUX 9.1 SUSE SLES 9 Vulnerability Type: remote code execution Severity (1-10): 7 SUSE Default Package: no Cross-References: CVE-2006-1614, CVE-2006-1615, CVE-2006-1630 Content of This Advisory: 1) Security Vulnerability Resolved: various security problems in clamav Problem Description 2) Solution or Work-Around 3) Special Instructions and Notes 4) Package Location and Checksums 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. 6) Authenticity Verification and Additional Information ______________________________________________________________________________ 1) Problem Description and Brief Discussion Clamav was updated to version 0.88.1 to fix the following security problems: - An integer overflow in the PE header parser (CVE-2006-1614). - Format string bugs in the logging code could potentially be exploited to execute arbitrary code (CVE-2006-1615). - Access to invalid memory could lead to a crash (CVE-2006-1630). 2) Solution orWork-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes None. 4) Package Location and Checksums The preferred method for installing security updates is to use the YaST Online Update (YOU) tool. YOU detects which updates are required and automatically performs the necessary steps to verify and install them. Alternatively, download the update packages for your distribution manually and verify their integrity by the methods listed in Section 6 of this announcement. Then install the packages using the command rpm -Fhv to apply the update, replacing with the filename of the downloaded RPM package. x86 Platform: SUSE LINUX 10.0: 840c489882c026a65cdf9b2c3bd23bf4 SUSE LINUX 9.3: fe1630ece8aa2a373a51a9424b198a40 SUSE LINUX 9.2: 85866ed8dd299d859a8c3af8994675fa SUSE LINUX 9.1: 16e8df6c4f6600de31a09a1465706d59 Power PC Platform: SUSE LINUX 10.0: 57cfa5135ad913b70b3aace346cfb5b5 x86-64 Platform: SUSE LINUX 10.0: ad2b04a8f5fbb2ced60255ec61a2065a SUSE LINUX 9.3: 796d039988817df8889687c374e62a33 SUSE LINUX 9.2: 43faff2546c2e88d3be55a99460bdd3e SUSE LINUX 9.1: 72796a06aea7faf1f7890db2df110d22 Sources: SUSE LINUX 10.0: a5c0fc2391f58c6888bb088631c275c4 SUSE LINUX 9.3: 27f4a7250e9dd00bb10dcded28c94d52 SUSE LINUX 9.2: 709a5ce55d1211838994a01dd16cc784 SUSE LINUX 9.1: a75522d97f96e58f87cebee5e7647649 c5a20f91051ae5844a6b09b3ba9dd9a5 Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: ______________________________________________________________________________ 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security SummaryReport. ______________________________________________________________________________ 6) Authenticity Verification and Additional Information - Announcement authenticity verification: SUSE security announcements are published via mailing lists and on Web sites. The authenticity and integrity of a SUSE security announcement is guaranteed by a cryptographic signature in each announcement. All SUSE security announcements are published with a valid signature. To verify the signature of the announcement, save it as text into a file and run the command gpg --verify replacing with the name of the file where you saved the announcement. The output for a valid signature looks like: gpg: Signature made using RSA key ID 3D25D3D9 gpg: Good signature from "SuSE Security Team " where is replaced by the date the document was signed. If the security team's key is not contained in your key ring, you can import it from the first installation CD. To import the key, use the command gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc - Package authenticity verification: SUSE update packages are available on many mirror FTP servers all over the world. While this service is considered valuable and important to the free and open source software community, the authenticity and the integrity of a package needs to be verified to ensure that it has not been tampered with. There are two verification methods that can be used independently from each other to prove the authenticity of a downloaded file or RPM package: 1) Using the internal gpg signatures of the rpm package 2) MD5 checksums as provided in this announcement 1) The internal rpm package signatures provide an easy way to verify the authenticity of an RPM package. Use the command rpm -v --checksig to verify the signature of the package, replacing with the filename of the RPM package downloaded. The package isunmodified if it contains a valid signature from
Get the latest Linux and open source security news straight to your inbox.