-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: razor-agents
Announcement ID: SUSE-SA:2005:035
Date: Tue, 23 Jun 2005 09:00:00 +0000
Affected Products: 8.2, 9.0, 9.1, 9.2, 9.3
Vulnerability Type: remote denial of service
Severity (1-10): 4
SUSE Default Package: no
Cross-References: None.
Content of This Advisory:
1) Security Vulnerability Resolved:
denial of service attack against Vipuls razor
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
Several bugs were fixed in Vipuls Razor spam detection framework.
These bugs could lead to remote denial-of-service conditions due to
processing malformed messages and possible stepping into infinite
loops.
2) Solution or Work-Around
Please install the updated packages.
3) Special Instructions and Notes
Please restart any service using razor-agents.
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:
676b7c6d977f0ed2b92ba313fa269689
SUSE Linux 9.2:
fc88751db9c4a14e5fbf6221d4ec5ad9
SUSE Linux 9.1:
889f8c37bbc80d520d6c4ecbfeff1913
source rpm(s):
a49208f7438160852e1dff387a70beea
SUSE Linux 9.0:
7d831ac330b9ca512722ac1754ec3236
source rpm(s):
db088de6b5cb8a5b67dfa485fdd22991
SUSE Linux 8.2:
d96fc57ad82f716dd421f0bca1c45b57
source rpm(s):
982a7860c698f1ea9a554128ce34b45b
x86-64 Platform:
SUSE Linux 9.3:
a1cd46cabd6e45c8f9d5ad7405085d04
source rpm(s):
5f9642b047be597bfbed8229d3098e76
SUSE Linux 9.2:
18157e6d2a2582b9a45b3a62be18ddb5
source rpm(s):
7f9d70373765389ab8284bd274af6d2d
SUSE Linux 9.1:
a4824f88fcb85f610ca738b6c729744c
source rpm(s):
5b064357f7db0574e7b89add57a3738f
SUSE Linux 9.0:
6ecca2f0cd15f7804d04dac04ad22ce6
source rpm(s):
7765df46f6b332e835da33ab04784d6e
______________________________________________________________________________
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.
====================================================================
