-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: php4,php5
Announcement ID: SUSE-SA:2005:069
Date: Wed, 14 Dec 2005 16:00:00 +0000
Affected Products: SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE LINUX 9.1
SuSE Linux 9.0
SuSE Linux Enterprise Server 8
SUSE SLES 9
UnitedLinux 1.0
Vulnerability Type: remote code execution
Severity (1-10): 5
SUSE Default Package: no
Cross-References: CVE-2005-3353, CVE-2005-3389, CVE-2005-3390
CVE-2005-3391, CVE-2005-3392, CVE-2005-3883
Content of This Advisory:
1) Security Vulnerability Resolved:
various php issues
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 Summary Report
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
Updated PHP packages fix the following security issues:
- Stefan Esser found out that a bug in parse_str() could lead to
activation of register_globals (CVE-2005-3389) and additionally
that file uploads could overwrite $GLOBALS (CVE-2005-3390)
- Bugs in the exif code could lead to a crash (CVE-2005-3353)
- Missing safe_mode checks in image processing code and cURL
functions allowed to bypass safe_mode and open_basedir
(CVE-2005-3391)
- Information leakage via the virtual() function (CVE-2005-3392)
- Missing input sanitation in the mb_send_mail() function
potentially allowed to inject arbitrary mail headers (CVE-2005-3883)
The previous security update for php caused crashes when mod_rewrite
was used. The updated packages fix that problem as well.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
Please restart your web server 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.0:
93ccea4a7fbf020f9dbc2d8e7e30f187
68c9297edac3cf40f63de9ab86a78204
cbe4216ab9aeaa46edfec82f4ec83add
7350c203d1da7cef4f707c1bd05b1fe4
2cbedde45de41d2a4c6a04a70151ef87
89b18c2b44043b00ca2a5e0ecd952ea1
aef612df7108ac49bc4671d48a522cd4
89b36c0207d77a276574acb917979c6c
9cd086bfd7f2460f560283d116335809
86a99ad87a84ca890d7f0812d84ea443
91d317da31a61e8b892e04fc22533465
d84a4b1979db6a704e0e68e3cd0c4123
SUSE LINUX 9.3:
2b0004354040ee46589579bbe9a10b7d
256ffe4b0adcbdea070c31199d927b8b
2f011176ba78e8d9e6d6705e3c520d77
1fda5a79328ad176ba4f76c3125a216c
9d95adc9956ad6c9aeb55395e5802a28
b78bda5c1bc4a445980c85263ef4e6b6
65d8d310cddf9eec6bf86f247d916924
83b6fb72b0235ef975e0b5dc3add6ba0
5b35e2b85d62841bfb4ef753a1befff4
e2e4396e3332d8127521e7208174b761
ec7b2caaf0b6f75a67bcf59df581faf0
e4680ce4c81fe741acace8396270f73a
b77193abb614a761fc8efb4ac3e30f38
efd60d4c38cee0570d91da4ded07241d
da933de9fe8c6b51ba8a1037bb51270a
306ffc5f200768e241045b9feb841ff0
4f6a0c426370c2ed0163ba5a210b3b18
3debbdb828fd9b62f84e9aca19cbc911
18c017cc066aa5ef10b8676e3abb39cc
SUSE LINUX 9.2:
3ef70addd7a8dbefe0369ff5657c572f
7424b1900e37eb48927e937f6f46a754
4fcf09657edc278dc1300beb99b2be23
3240c192c6d3a2861c61fafc6f1e3dbe
bd21b0c6a8787c055bce1b4a0832e9c6
a15b1e13e8d4c508b20a0d9cb8db0e9a
29cb0b7455d85e855cdcff7ed3cf362a
378fbc8b49f96936c4a803dd2fcd9150
3e8482cdec483a0d97336d7ff875aca4
0e8aebcd5576f652c5460b8b5eb0eb59
SUSE LINUX 9.1:
03e74cf5c21690096b5c3c6d73db5edf
f3ff33b1c66c60e512668d071c2865a2
8ef9861fc1154dfb13b1a856d97ede58
4f44dbff22b3e61ded0cafa05e5dd8a4
1e61d5c750ceb6e5ca0155da26ad9d56
352b80414193b6e759a087a00e961f9e
a7dbbc68d8088e1c9446f5b3aa3efdf6
2d65af58903d5b57eb1a5c9da7a4d12c
fcca537fe7a10ffbc983631586af80e1
3f089876cee98edb6ca744ec16e8b348
c12867220bc31711bf858488ecf82652
2b13e53d9f834eae4c7f8f5dcd0309e6
35a0ed7a8ed2680f6795b55a17286a44
467cc0aecaeff74e01794a9796d7ae5b
d00467ec2ea75c736257ec747dbce964
fec07399b7946aa6fa282fdf3a11b7b5
SuSE Linux 9.0:
7e7f3acd96bd4ccfa449fa627d238e61
6ad974a6ef73c055042f2791511324a4
8062597ee1d901295f50ef7f3b210fd8
a26e3da082bb7af529bfe6a8863d3bea
b0c65694138fcc7e358a23578c81fc0f
a575ef3d3585d52457277fa1b1f52fc9
Power PC Platform:
SUSE LINUX 10.0:
b6fc10ae85b52c9fa8dfc1391cb5c42e
64b0b1929db34126fef1fe45477721c8
32e5df4ad82710e942229b352001062f
5731166b070555e3b12977f17c807164
2d5ab0d77fbeb8b4c2c2eb0054ef95db
e88e8df2e390d4f1de0420144120ffba
54988beb5795ec69b9477fb17bd05570
9f060cbb31f36448bf51baedd817dd95
3970e52026e0de1d22bcb1f0044fc7f4
97a445e95bbbffc0b73b8e5d812e3a7c
7a0713faac36b75d0c360a81ec1cd902
x86-64 Platform:
SUSE LINUX 10.0:
c19815f1d3dd1837db7d084d40c0bd5f
e6f97e4a7f21ac06648b7687ae44c9c0
97b0538d2f776379b9ed53603e7c7c02
6910814d7b4f55e46e56fcbfc2605e7a
93fc59c57c83d493d9b75735b53f59dc
84357282e66154125e738f958c5f8a1d
a61b2ef113fa1bc4d95d18a2de10c037
c1d603229a890d512c6965a9bf93e0ae
3258488c43c3ceba6cac3e079adfd9dc
07f02223a220056e989f1ffcdb5bb301
f04093dc74fc362b775a76826c4e5b70
b47b507bb86fc499b57a50ea8d96cf4e
8998ff285408d6aa7194631b9158bc95
SUSE LINUX 9.3:
f572808e11f11e832d5af73789639d13
78b816f654dba3203f59574403c5b015
b89d13e866e3331a909acac41032856b
24f56083bfec12dfa8f81d122ce76b59
04feac8fb5cca0eb1b2a63c09712d2a1
96b5f6889bfd704b35bee5b503037f98
a0543150af489560130081c8f8bc00a5
e1e5f5cb50bbc96ac619c06bd9b40c6c
9e71c63f8f77220d264675a93d9be64e
77f30df59a934c9097e1ff5ca2f9ef82
0763a366fa64f3a9f9451ecf8092060a
e4b848f275c2720f0ea9a583245bdfd4
a5f4693e50e97ba9b2abc4a74fcfc433
318c22c0cc73fc23e1521ebf90614d49
1204d8a49841ee632afb3a31ea6786d5
9673ca446863d44d8b3070f4b4605c8d
777c96c8250371403af09dc8ce68578e
4843edaf660f33f032bf06f9a0c70e0d
75326499903800ea00ccef6de32df243
10fcaf8375a8d3d53b2b4d6c6799fb5c
SUSE LINUX 9.2:
995add6961cbaaa3e93ecc3fd4d4414e
29be09a1b44c9de9475184043915f9d3
d56c620f8e0f47b86b644bf35a2fb218
9904439aebaa54e0a32738ca6d914671
78e991160557cef261f93b867d3e3506
4c0d5054c3fc50eff7f6f1e28cca84f2
cd555396599de66c5b8bb69bbf531c01
25495dcc55f44a5a87b7523a18bd547e
0142a90e52aad3f21a9957d5e657ceb1
9bccf3bdf6c86e25e1472e740096d4a1
6cb88042269a72253f474311f1ddf2ab
SUSE LINUX 9.1:
c518162fd01a4dfbcd67826b43b04d1c
963d63c4c9ccedd60d78066056021da5
43f29e791ecde3421a6160a5efef1460
9f148f7b01206e4064e31c5bf1126e3a
31c00f890667c18d9f4b5d6db8e34c23
280203830ba42b1883eb9a0488d1a51a
a150e72f55d123e82445d8584c8580af
955c5212e05129555e4f669e29abf206
c4b625a5b45cd9c1cf983b96a5eb5857
a42f92a755f2a27f30d365e987fc07c0
5fe41e7a9ce219521abb7118e06acd06
4e7c18b9c384f9925be4475b2a58d7ae
409cd0a641f4af01bcec0eee89d730ed
2c8027c2e1b13ba79684d22599441f98
60f76ba962ff878a122c9713b3648acb
9eb2f1367e1a24552a8cedfb6bc506f0
SuSE Linux 9.0:
201cdcb6ac370ba24bf028ff973e2d78
200e27434b84dda66a8d7072639d50d3
bebf84684f3d4e2e246e9e0968e1c9e9
c13dd768ed49a6b356fea34b0bee22b7
76402dba0b5cd93d01121f7cdaccf0a8
911132503ce437c56fc149ceaca84fc0
Sources:
SUSE LINUX 10.0:
df71d97d15a80d697e2bb4bde7045f7e
b8982a91a4434d6d8a5e6682d156ec89
SUSE LINUX 9.3:
4fda8297cdd055ca5ea5f25c5fd34f7f
00bbae3e2df2e260419636d09124072f
SUSE LINUX 9.2:
2ffe97003b66122df2c66282df7c191f
SUSE LINUX 9.1:
976c480089d6bbb93c8382024befa2b0
254dafb4323f39a6d5833b5821888be3
SuSE Linux 9.0:
1ac608916ba50d061a5d0a9dcc5bf5f1
55aeee3d79a95d4b77c1c9491b6a0216
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
https://www.suse.com:443/
https://www.suse.com:443/
https://www.suse.com:443/
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
- See 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.
====================================================================
