-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: clamav
Announcement ID: SUSE-SA:2007:026
Date: Fri, 20 Apr 2007 15:00:00 +0000
Affected Products: SUSE LINUX 9.3
SUSE LINUX 10.0
SUSE LINUX 10.1
openSUSE 10.2
SUSE SLES 9
Open Enterprise Server
Novell Linux POS 9
SUSE SLES 10
Vulnerability Type: remote code execution
Severity (1-10): 7
SUSE Default Package: no
Cross-References: CVE-2007-1745, CVE-2007-1997
Content of This Advisory:
1) Security Vulnerability Resolved:
clamav version upgrade to 0.90.2
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
The AntiVirus scan engine clamav was updated to version 0.90.2. Among
other bugs two security problems were fixed which could cause a remote
denial of service attack against clamav or potentially be used to
execute code.
- CVE-2007-1745: The chm_decompress_stream function in
libclamav/chmunpack.c leaks file descriptors, which has unknown
impact and attack vectors involving a crafted CHM file.
- CVE-2007-1997: Integer signedness error in the (1) cab_unstore and
(2) cab_extract functions in libclamav/cab.c might allow remote
attackers to execute arbitrary code via a crafted CHM file that
contains a negative integer, which passes a signed comparison and
leads to a stack-based buffer overflow.
Updates for this problem were released on Tuesday April 17.
2) Solution or Work-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:
openSUSE 10.2:
665649e5d1b5f2e2ec072ff6e5acff96
SUSE LINUX 10.1:
a3e3616c1dd19b09be4ae1be22279221
SUSE LINUX 10.0:
3a1aefec54a30a216a46399d46c4dfa5
SUSE LINUX 9.3:
31696e4e0837aab02429695bbb11093d
Power PC Platform:
openSUSE 10.2:
1a497a6200da361e3799f4f2ab4091e7
SUSE LINUX 10.1:
12c6ed4e2cbb5405838deb2e22bced54
SUSE LINUX 10.0:
704a40de922c2eb8c5841c40fe19050c
x86-64 Platform:
openSUSE 10.2:
641d35e63c0ce45bb86099a4a26d4fe6
SUSE LINUX 10.1:
14ee14fc3cbcf9f08937b97998441bef
SUSE LINUX 10.0:
ca599326fc97e05e41e6ac793ee63c21
SUSE LINUX 9.3:
1a00a64d6b88ce2465b65d61cf2031ed
Sources:
openSUSE 10.2:
2d24ba99281475f4884dd706dea265c9
SUSE LINUX 10.1:
7bc311314710d124861172e485056ccd
SUSE LINUX 10.0:
99ac20be92f82f512d5f4a59feee6460
SUSE LINUX 9.3:
7cdb83cd4f29d4963cf4fa563b51d9fc
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
Open Enterprise Server
http://support.novell.com/techcenter/psdb/50a5cb718f20761dd7e0b6b4e0935c52.html
Novell Linux POS 9
http://support.novell.com/techcenter/psdb/50a5cb718f20761dd7e0b6b4e0935c52.html
SUSE SLES 10
http://support.novell.com/techcenter/psdb/50a5cb718f20761dd7e0b6b4e0935c52.html
SUSE SLES 9
http://support.novell.com/techcenter/psdb/50a5cb718f20761dd7e0b6b4e0935c52.html
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
See SUSE Security Summary Report.
______________________________________________________________________________
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 is unmodified if it
contains a valid signature from build@suse.de with the key ID 9C800ACA.
This key is automatically imported into the RPM database (on
RPMv4-based distributions) and the gpg key ring of 'root' during
installation. You can also find it on the first installation CD and at
the end of this announcement.
2) If you need an alternative means of verification, use the md5sum
command to verify the authenticity of the packages. Execute the command
md5sum
after you downloaded the file from a SUSE FTP server or its mirrors.
Then compare the resulting md5sum with the one that is listed in the
SUSE security announcement. Because the announcement containing the
checksums is cryptographically signed (by security@suse.de), the
checksums show proof of the authenticity of the package if the
signature of the announcement is valid. Note that the md5 sums
published in the SUSE Security Announcements are valid for the
respective packages only. Newer versions of these packages cannot be
verified.
- SUSE runs two security mailing lists to which any interested party may
subscribe:
opensuse-security@opensuse.org
- General Linux and SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an e-mail to
.
suse-security-announce@suse.com
- SUSE's announce-only mailing list.
Only SUSE's security announcements are sent to this list.
To subscribe, send an e-mail to
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================
