-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: clamav
Announcement ID: SUSE-SA:2005:038
Date: Wed, 29 Jun 2005 13:00:00 +0000
Affected Products: 9.1, 9.2, 9.3
SUSE Linux Enterprise Server 9
Vulnerability Type: remote denial of service
Severity (1-10): 5
SUSE Default Package: no
Cross-References: CAN-2005-2070
CAN-2005-2056
Content of This Advisory:
1) Security Vulnerability Resolved:
clamav various security and bug fixes
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
This security update upgrades the Clamav virus scan engine to
the version 0.68.1.
Among other bugfixes and improvements, this update fixes a bug in the
Quantum decompressor routines that can be used for a remote denial
of service attack against clamd.
This bug is tracked by the Mitre CVE ID CAN-2005-2056.
Also the Clam AV Mail Filter (clamav-milter) Plugin when used in sendmail
could be used for a remote denial of service attack.
This bug is tracked by the Mitre CVE ID CAN-2005-2070.
2) Solution or Work-Around
Please install the upgraded packages.
3) Special Instructions and Notes
Make sure you restart all services using clamav.
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.
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web.
x86 Platform:
SUSE Linux 9.3:
38e12ca1dce7b58b849850ad7f211391
21d73753323d5c5766d532e123b38704
SUSE Linux 9.2:
159c4c2763dd901c4dfe100ae92aad24
ce2ecb1fa77d8ec5b18d08a79c50a835
SUSE Linux 9.1:
d5c0f87913be6d566deb949512494219
source rpm(s):
04a1f51626c34212289ecd78cfa86ffb
x86-64 Platform:
SUSE Linux 9.3:
d7a12619a5b7ff6f4e64a98cbe15a5b2
078ab644d16fff2e74826c56971f035f
source rpm(s):
a48c8535c90ad21b386e0578249bbe6e
SUSE Linux 9.2:
7b8d28ad51f9070af368e1fda08058df
3f07c2f15a2c911e6d1656788ffd14d3
source rpm(s):
e9651a93e9afc7e6a21da7a719ca3067
SUSE Linux 9.1:
311638776159430b8fb2dd2893615892
source rpm(s):
6c0653449afaf744459e80b1131d889b
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
______________________________________________________________________________
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.
====================================================================
