-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: clamav
Announcement ID: SUSE-SA:2006:046
Date: Wed, 09 Aug 2006 16:00:00 +0000
Affected Products: 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): 5
SUSE Default Package: no
Cross-References: CVE-2006-4018
Content of This Advisory:
1) Security Vulnerability Resolved:
clamav heap buffer overflow
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
Damian Put discovered a bug in the UPX decoder used for scanning UPX
compressed Windows executables. The bug allows for a heap buffer
overflow and may potentially be exploitable to execute arbitrary
code. ClamAV has been version updated to version 0.88.4 in order to
fix this problem.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
If you use clamd or freshclam please restart them after the update
if that didn't happen automatically.
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:
d782f3c2ec62fca80cbb1f2bb531b758
SUSE LINUX 10.0:
2506a173ae698bbb85077edd252bd537
SUSE LINUX 9.3:
0cd9e4ae7f3aeeff26cad68d2fbd4ea9
SUSE LINUX 9.2:
1f2c24cc49f1bec6b8bf1f4ad0e3be04
Power PC Platform:
SUSE LINUX 10.1:
466de7dbb509ed9e1d049fe4d1748d6c
SUSE LINUX 10.0:
294827d288e5d409fbcbe80b1bcd4a01
x86-64 Platform:
SUSE LINUX 10.1:
92bd2caca792c63f3e074998e0f2966e
SUSE LINUX 10.0:
e200bb4c9de2706d4a549869fea85dc6
SUSE LINUX 9.3:
4ff1d40fc1721bb6d4930c582ad27bfd
SUSE LINUX 9.2:
4fdf8b51963cd0460b7a2febf056003c
Sources:
SUSE LINUX 10.1:
071e56397a105c1ec8fb99937aba6b7d
SUSE LINUX 10.0:
183529f6fb8098c5cd592bfaf0841f5d
SUSE LINUX 9.3:
95fd6765b9ac67100b81ac321daf2867
SUSE LINUX 9.2:
0759b1e53d0148b2ad372d33ed3d1135
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
SUSE SLES 9
SUSE SLES 10
______________________________________________________________________________
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.
====================================================================
