-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: clamav
Announcement ID: SUSE-SA:2006:060
Date: Wed, 18 Oct 2006 18:00:00 +0000
Affected Products: Novell Linux POS 9
Open Enterprise Server
SUSE LINUX 10.1
SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE SLES 10
SUSE SLES 9
Vulnerability Type: remote code execution
Severity (1-10): 6
SUSE Default Package: no
Cross-References: CVE-2006-4182, CVE-2006-5295
Content of This Advisory:
1) Security Vulnerability Resolved:
two clamav security problems
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
Two security problems have been found and fixed in the anti virus
scan engine "clamav", which could be used by remote attackers sending prepared E-Mails containing special crafted infected files
to potentially execute code.
CVE-2006-4182: A problem in dealing with PE (Portable Executables aka
Windows .EXE) files could result in an integer overflow, causing a heap
overflow, which could be used by attackers to potentially execute code.
CVE-2006-5295: A problem in dealing with CHM (compressed help file)
exists that could cause an invalid memory read, causing the clamav
engine to crash.
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:
SUSE LINUX 10.1:
964cf3a6dd5b0f2a6d9dc64157da8161
SUSE LINUX 10.0:
cb4b120a6bae0e0fbe01b4da1afe8a8d
SUSE LINUX 9.3:
80983b2e847814bf520353d2323096a8
SUSE LINUX 9.2:
9906e32e0d30e1ca635cb3cf24ded93e
Power PC Platform:
SUSE LINUX 10.1:
8444302c83bde8c05ad0b364c1c44052
SUSE LINUX 10.0:
d8b9cba427fd384801fdb553f0f20fcf
x86-64 Platform:
SUSE LINUX 10.1:
cd8a450d769a8917e88abfec37d3e96a
SUSE LINUX 10.0:
5a007b8d4f873499f4137fcebee86603
SUSE LINUX 9.3:
e6ec8962851ae738a7c964103f655d74
SUSE LINUX 9.2:
6a8d3f8b6be490ee0772a03f776e8198
Sources:
SUSE LINUX 10.1:
afe46b41ae34d657ce2cc0c311e9efd9
SUSE LINUX 10.0:
623389716f793a3c477e8abe2cd4bdd9
SUSE LINUX 9.3:
27232143bbf2b4d030029af3a1f77b41
SUSE LINUX 9.2:
da36e3d0a72dabcc16d17fed71ee2cee
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/9052e142ab5cfd0891d67dee5c2e95e6.html
Novell Linux POS 9
http://support.novell.com/techcenter/psdb/9052e142ab5cfd0891d67dee5c2e95e6.html
SUSE SLES 10
http://support.novell.com/techcenter/psdb/9052e142ab5cfd0891d67dee5c2e95e6.html
SUSE SLES 9
http://support.novell.com/techcenter/psdb/9052e142ab5cfd0891d67dee5c2e95e6.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:
suse-security@suse.com
- 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
.
For general information or the frequently asked questions (FAQ),
send mail to or
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================
