-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: pcre
Announcement ID: SUSE-SA:2005:048
Date: Tue, 30 Aug 2005 15:00:00 +0000
Affected Products: 9.0, 9.1, 9.2, 9.3
SUSE Linux Desktop 1.0
SUSE Linux Enterprise Server 8, 9
Novell Linux Desktop 9
Vulnerability Type: remote code execution
Severity (1-10): 6
SUSE Default Package: yes
Cross-References: CAN-2005-2491
Content of This Advisory:
1) Security Vulnerability Resolved:
pcre integer overflow 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:
none
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
A vulnerability was found in the PCRE regular expression handling
library which allows an attacker to crash or overflow a buffer in the
program by specifying a special regular expression.
Since this library is used in a large number of packages, including
apache2, php4, exim, postfix and similar, a remote attack could be
possible.
This is tracked by the Mitre CVE ID CAN-2005-2491.
2) Solution or Work-Around
Install the updated packages.
3) Special Instructions and Notes
Please make sure you restart services linked against the pcre library (apache, exim, postfix).
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:
ccc4711c80659d57a7d06754d577a33c
18ad1553287682ad09b2412dd038c5c5
0246d39b1aa7bbfa8872a4f841d2842f
SUSE Linux 9.2:
d1c4af6faceecbbc028c5c5b32cd46bd
276ecc193b12cf20e5ac1e2be2e9484c
107c8c3ac5218348e89cc5d6a235f34d
SUSE Linux 9.1:
0330a3dd845c33bd460851e13abdcb01
ca1722d18e465cce1e6be5fc69a97586
2933451df49a408b53d9d2628fd74d38
source rpm(s):
131e5f816d7f9e6e8536416e574a2e07
SUSE Linux 9.0:
7f6492b3fdd2e9cf9ff104c7ef366fd2
c1e36f246764869a672f3e69c879a976
7e4d12f5af0bc2a68d21a8d72ccb1d37
source rpm(s):
367ad88cdd0c0ec060992312e96a9997
x86-64 Platform:
SUSE Linux 9.3:
36c7d2b3713c27c79292a7637443a285
db8e83e2867c3d2f713a43705b655ffe
source rpm(s):
b4d17fa6f1f4359196b04495a7d6fb19
SUSE Linux 9.2:
dcaeeb4225fb820c85927dd2104c9f9f
bcbcb9ec334e1a8896ca29b3c10a5a72
source rpm(s):
096c4732ffd1c34e424ee62b86fcb741
SUSE Linux 9.1:
167f6794525cdb24cc6d0fe16c7d3baf
a1a105c4c60d7c2e0745d6d81b24afef
source rpm(s):
4186754b93b1e2856d2dbb83be5fb6f5
SUSE Linux 9.0:
0884bc87e09d1607e80d98ab7c898549
a336cf08fe6b8e4818480304bd63cfb6
source rpm(s):
308b513ff579695f0292b881d7022f8f
______________________________________________________________________________
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.
====================================================================
