-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: clamav
Announcement ID: SUSE-SA:2007:033
Date: Wed, 06 Jun 2007 15:00:00 +0000
Affected Products: SUSE LINUX 10.0
SUSE LINUX 10.1
openSUSE 10.2
SUSE SLES 9
Open Enterprise Server
Novell Linux POS 9
Vulnerability Type: remote denial of service
Severity (1-10): 6
SUSE Default Package: no
Cross-References: CVE-2007-2650, CVE-2007-3023, CVE-2007-3024
Content of This Advisory:
1) Security Vulnerability Resolved:
clamav security update
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 anti-virus scan engine ClamAV was upgraded to version 0.90.3 to
fix several security bugs:
- Wrong calculation of buffer-end (CVE-2007-3023)
- Use strict permissions for temporary files (CVE-2007-3024)
- Heap corruption causing denial-of-service with corrupted rar archive
(no CVE assigned at this time)
- Detect block list loop in OLE2 scanner (CVE-2007-2650)
Updated clamav packages for SUSE Linux Enterprise 10 will be released
after Service Pack 1 is released.
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:
a8a37e2d3ccd914f91597f8f48cca99f
fc9519bd40748e2d30037596375b5cca
SUSE LINUX 10.1:
31d196d6eaf5c0c8f29dc4c21e4ff78d
SUSE LINUX 10.0:
02e6bdaef4c68c484179275b0bee985f
3191c5e50ffa62bdf817b65368786c8b
Power PC Platform:
openSUSE 10.2:
583fdbffc1e5069973eacc34c4de2947
29c2788eb45087ee974fad983f1b4964
SUSE LINUX 10.1:
320d1bcc7a5e6718b95c368f7b1d4d7d
SUSE LINUX 10.0:
2b43aa34e2d3c302da79759f242cf91e
ec1ae4d5d638bd223cf33e551bb382a7
x86-64 Platform:
openSUSE 10.2:
5a4b81479f025c99e304794b0c5b0c27
a81e693c4c371f6af4f98cfad4d615b5
SUSE LINUX 10.1:
a42e875ca5f71ec7d7efab625d13b9e5
SUSE LINUX 10.0:
a75c1378b9a05f54a699996345e9b174
702683c41d6ab2dd17acd3fcb2f2d163
Sources:
openSUSE 10.2:
3a018d00982f611bc847fcdbf3be0545
SUSE LINUX 10.1:
2be2b9659f5bb2fe11e32fb98a409d37
SUSE LINUX 10.0:
2bd465210eed5eaa70fe16c1a64fed75
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/5a3e85703885a03d41664f02c24200e0.html
Novell Linux POS 9
http://support.novell.com/techcenter/psdb/5a3e85703885a03d41664f02c24200e0.html
SUSE SLES 9
http://support.novell.com/techcenter/psdb/5a3e85703885a03d41664f02c24200e0.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.
====================================================================
