-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: apache2
Announcement ID: SUSE-SA:2006:051
Date: Fri, 08 Sep 2006 16:00:00 +0000
Affected Products: Novell Linux POS 9
Open Enterprise Server
SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE SLES 9
Vulnerability Type: cryptographic problems
Severity (1-10): 5
SUSE Default Package: no
Cross-References: CVE-2005-2700, CVE-2005-3357, CVE-2006-3918
Content of This Advisory:
1) Security Vulnerability Resolved:
Apache2 security update
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 web server Apache2 has been updated to fix several security issues:
The security fix for CVE-2005-3357 (denial of service) broke the
earlier security fix for SSL verification (CVE-2005-2700). This
problem has been corrected.
Additionally a cross site scripting bug with the "Expect" header error
reporting was fixed (CVE-2006-3918). The Apache foundation does not
consider this a security problem.
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.0:
4e5f7482e476e85e92df04868fda661c
56fc5c08895d0a9a3c2cc6015b3dd34b
8b1c3a66cbad2f102b1569f3e0333501
SUSE LINUX 9.3:
a2aa08e4ddd70859ec542aed22ccdee9
bf0ceb6357957c5e0565857dbf544ea3
eddf464f0073f6d1b3576fa5ef0b5c8b
SUSE LINUX 9.2:
3d7ae24eeb12d37484db873829cad192
7ac171bd3c9fe75cb96d18038b63c1f6
9e6cecbb28ae31c0693e3cb849a75f8f
Power PC Platform:
SUSE LINUX 10.0:
c0690dee4b47c8ece321996832397915
4cb7734bcf6c5c1de524ac1b3bc183b2
c1e262a0f1dd27c7d4da0919070f53a1
x86-64 Platform:
SUSE LINUX 10.0:
5a11e9b78e0f946403c47797fb4e49b9
b05190443513cea99aafd1a15baf3ddc
9248815b04fc1a26950d33c5bcc6b85f
SUSE LINUX 9.3:
6ce32141596325584f13a18f0271269c
dfddc46d4b6feab89f35a579d5471533
de9fb2bd70949d79cc5f020f72beca37
SUSE LINUX 9.2:
632e9b785b32694a141d0b89d27ac489
b63783a1c93a875064f56f55151acf81
43ffab89ba259f707edc199ed54eee57
Sources:
SUSE LINUX 10.0:
ae34902816649e317fd03afd1a185565
SUSE LINUX 9.3:
a4da14a77b4c58a07cd0fcf9e324b3ed
SUSE LINUX 9.2:
ab9adcf8c71117ed3cb9f1ba75b2138a
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/798e9e22eaf4a4eed570f26abfab9f02.html
Novell Linux POS 9
http://support.novell.com/techcenter/psdb/798e9e22eaf4a4eed570f26abfab9f02.html
SUSE SLES 9
http://support.novell.com/techcenter/psdb/798e9e22eaf4a4eed570f26abfab9f02.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.
====================================================================
