-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: clamav
Announcement ID: SUSE-SA:2007:017
Date: Fri, 23 Feb 2007 16: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 denial of service
Severity (1-10): 6
SUSE Default Package: no
Cross-References: CVE-2007-0897, CVE-2007-0898
Content of This Advisory:
1) Security Vulnerability Resolved:
clamav 0.90 security fix release
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 updated to the version 0.90 to
fix various bugs including 2 security bugs:
CVE-2007-0897: A file descriptor leak in the handling of CAB files can
lead to a denial of service attack against the clamd scanner daemon
caused by remote attackers.
CVE-2007-0898: A directory traversal in handling of MIME E-Mail headers could be used by remote attackers to overwrite local files owned
by the user under which clamd is running.
Since clamd is running as "vscan" user on SUSE, it would only be able to
overwrite files owned by "vscan".
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
Note that the configuration file format was changed by the upstream
clamav developers.
We included a converter script which automatically converts clamd.conf
and freshclam.conf on update but we suggest to review the changed
configuration files.
Please check that the clamd is still running after the update (it
should get restarted automatically by the update, but might fail due
to incorrectly converted config files).
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:
450fd88ce94fb7421d7232e55ca7be57
SUSE LINUX 10.1:
9bb705eef58f149c6023fa25a2e7441d
SUSE LINUX 10.0:
abe77980ac3d274549acef965d9b3ed5
SUSE LINUX 9.3:
d0ab2a48d370941ee4037ffab8686916
Power PC Platform:
openSUSE 10.2:
506b432229252c3188a977c46c847ef9
SUSE LINUX 10.1:
4de0855522f57a533bdb770e6c760abf
SUSE LINUX 10.0:
b0b11ecfb27387259b0589f943dc6bd2
x86-64 Platform:
openSUSE 10.2:
c6d88b70c377db486524e8331cc19ded
SUSE LINUX 10.1:
9eb79478b0a8d83370fabcf43e47b5ae
SUSE LINUX 10.0:
fbe3ec3733c4483c5b7dfd890d5a6079
SUSE LINUX 9.3:
cd744ebc2447166b5cc7bd065a93c4b5
Sources:
openSUSE 10.2:
ab8ddfd395ab7fccde2e152e13d4e5a1
SUSE LINUX 10.1:
1f43996fcef6f47298ea8fcc2ea07eaa
SUSE LINUX 10.0:
9d7f916f64ce377bec6a531d9fa74590
SUSE LINUX 9.3:
9887574f7864200081f230fa32e78db8
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
Open Enterprise Server
Novell Linux POS 9
SUSE SLES 10
SUSE SLES 9
http://support.novell.com/techcenter/psdb/abe28be29295a2d1e392e79ff39d4b40.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.
====================================================================
