-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: apache,apache2
Announcement ID: SUSE-SA:2006:043
Date: Fri, 28 Jul 2006 17:00:00 +0000
Affected Products: SLE SDK 10
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 denial of service
Severity (1-10): 6
SUSE Default Package: yes
Cross-References: CVE-2005-3352, CVE-2006-3747
Content of This Advisory:
1) Security Vulnerability Resolved:
Apache off by one security problem
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 following security problem was fixed in the Apache and Apache 2
web servers:
mod_rewrite: Fix an off-by-one security problem in the ldap scheme
handling. For some RewriteRules this could lead to a pointer being
written out of bounds. Depending on stack alignment this could be
used to potentially execute code.
The mod_rewrite module is not enabled per default in our packages.
This problem is tracked by the Mitre CVE ID CVE-2006-3747.
A more detailed description of this problem is available in:
For SUSE Linux 10.0, 10.1 and SUSE Linux Enterprise 10 additionally
a old bug was fixed that we missed to forward port to the Apache 2.2
packages:
mod_imap: Fixes a cross-site-scripting bug in the imagemap module.
This issue is tracked by the Mitre CVE ID CVE-2005-3352.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
Please close and restart all running instances of Apache after the update.
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:
124342d5311b318586d91d12117bdd2a
4a73ae89777943f4127743f817f0a0a5
1905af7f606986f1818ebed5bd3382d5
SUSE LINUX 10.0:
adf6c8665b9f0f36c6a7720a8f1bfad1
1cbcec6896dc46504140177b48ca014d
f721e397c518cc6160886a1296e5a109
SUSE LINUX 9.3:
e6ae2ee1353c1f1c31c0595b60d18137
cb02c5f97671d2ab0a64215ed9987c2f
b8872991cf54d99659e60d860d0c44e8
SUSE LINUX 9.2:
9365d403839e7c0740aae1e2f1b6cdfc
97d506d68996f80ffaaaa6494a127f7c
f649e8eb98d43d6a44231f0c7453c9b2
Power PC Platform:
SUSE LINUX 10.1:
133b02c7a3a52a2bf144ece351ba00a1
099056b7a0f634ff1daf583ce2163839
a22ae78408cedfea6d66362509d3c721
SUSE LINUX 10.0:
16a119e6dab8e972a992ef37bd9973aa
fcb8c3ca92f1b9a39791f51aad5b8907
0f5dff953aea37964958bc0ed8932412
x86-64 Platform:
SUSE LINUX 10.1:
3ab36db089d7f3d60a7114820970afdd
b7e9bc09fe9684292acf0e7ed0218b14
b6b1ab1c03073f7f2acc07a0231ea532
SUSE LINUX 10.0:
17c4bdc7577446bf45335ba58ebb3513
d55a93a86ae6b5bf037ee336d4307133
e64fc86d3337913db0c22ffde3519a36
SUSE LINUX 9.3:
d4996884e49ef11d27c97340efb6f079
5b599e78e59c7b59dc199777fe2c4eea
09f0f1dc18761a8a902f2dc5ab166883
SUSE LINUX 9.2:
595101ab05dfe5117ddab1d1f1463a28
112fe5dd14b66a4fbb82c3c5178bef69
7c07b8b400e6ed13a4707c3ebe1eed3a
Sources:
SUSE LINUX 10.1:
493d11cc099e975bc0974611cf936816
SUSE LINUX 10.0:
b83da64c6ad0b76d7a3a8bf909d61d39
SUSE LINUX 9.3:
5d4c85c7f60ea5c73df0fba7d92bec35
SUSE LINUX 9.2:
2c4e95c0ebe9bee49dec733cbdeb42d3
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
SUSE SLES 10
SLE SDK 10
SUSE SLES 9
______________________________________________________________________________
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.
====================================================================
