-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: php/pear XML::RPC
Announcement ID: SUSE-SA:2005:041
Date: Fri, 08 Jul 2005 16:00:00 +0000
Affected Products: 8.2, 9.0, 9.1, 9.2, 9.3
SUSE Linux Enterprise Server 9
Vulnerability Type: remote code execution
Severity (1-10): 6
SUSE Default Package: no
Cross-References: CAN-2005-1921
Content of This Advisory:
1) Security Vulnerability Resolved:
PHP XML::RPC code injection vulnerability
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
A bug in the PEAR::XML_RPC library allowed remote attackers to
pass arbitrary PHP code to the eval() function.
The updated php packages fix the XML::RPC bug, however several third
party PHP packages include a copy of the problematic XML::RPC code
itself and might be still vulnerable after the update.
Please check their respective websites whether the package is
vulnerable.
The following projects are known to include the XML::RPC code:
- tikiwiki
- postnuke
- drupal
- b2evolution
- b2
- phpGroupWare
- eGroupware
- Serendipity Weblog
- phpAdsNew
- Max Media Manager
This issue is tracked by the Mitre CVE ID CAN-2005-1921.
The bug in the SUSE php packages affects SUSE Linux versions from 8.2
up to 9.3, SUSE Linux Enterprise Server 9 and Open Enterprise Server.
php4 on SUSE Linux Enterprise Server 8 is not affected, since it was
not shipping the XML::RPC extension.
2) Solution or Work-Around
Please install the updated packages.
3) Special Instructions and Notes
Make sure that all PHP projects you installed additionally have the
XML RPC flaw fixed.
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:
6ceb12d50de0b3d64da8e729d49e28c0
20d09cc7000e3249f662c77f2eb75085
60e214f227b6da8297a73a6d1acc29a0
6f2cdf6f6febe9b562b1435cf4ff57be
a22e97ac02e87da1e37556ae383a6e57
fe9b58e62bdc17ef2fdc661f771d84ba
2bc6962c584f435dcb57869b5972a633
a1fdae81e0eb168d4c313afa0cbe9098
f158545c61aa1cbc73f9b57c24fc8c2a
c12e433ce5b96d23f6fafea0ff85fb94
67461b805f48580e24f9620e0d300e0b
1df77fcb3c89ae908b9d705b72f4c188
7d077071cb7d16a114cd718462a0c0c4
174e3e3a78da89366adb9192188bd883
07ea2b721521e53395ccfcd2955787a2
07a7568688fa7de8be5c5cef200a71bf
ae640530992eff2a4e7849f6b1dd13a9
4ee74dbf8b2beb06d06cd007829dd95c
SUSE Linux 9.2:
3d220a9d7050ca574f9795bb6fb6c568
e7b2dc34a9e1fd9292fb637d2a50b3f0
7d0559306e95bb4849b3bb1e540fe707
25c54dd405f9ef11e003139132dec5ce
858c0fbb01d69791cc790fa88fa43be5
d12455f4b27f5f43472d3b55a1908c94
77f88189f5577677e85fecb056864b01
dbe18e050fb2d691fde51d5f19b31299
0bfbfb6be77c5dd18d003edf11ab372f
a37fd3e3c384a245b96c8074133b271a
SUSE Linux 9.1:
58cfea5e0d3e9129f0b3e427db9dfabf
da907cdaa0bec054d9a78901acb42e80
2a67bfe37386d906a33fe1d5e18cd0b9
765242729f4f9e50fc0edb04a61eac83
0b84281d91e9fccf3840c8b849e95183
7dd06a00f923dfbe148b051cba263535
6a598bf4b4acf02488168780ad6c6111
20b1062090ad8573ac8e45dedf83b13f
35f03b50591ba20cc54e9fce9c0551a8
29b9511a283f380b447141f6e099f573
92b46089b8999f000978c155a240f015
734431254ee4aafb3589c2d7b1309275
e2a42b2935762f032c75a16c25bcb72c
92915af3f771a03e3d68bf853bb8445b
9db317e3008538c274c895b79cb8e96b
source rpm(s):
9cf307f4e6f00f1c2eb1b8f4791bd456
SUSE Linux 9.0:
cf7009c567ce43e193c0dae046544991
18e29331624042ff788ad4980532bd56
a24647c026e3af5f7a3d60f86a2af9fb
9077be213ec13ffcec35bc3b9dd1adf9
fb830b7a4f111c3234ccdef19a6ec43a
dab4bc4cec1b807dbdbac4ac24bc55a6
source rpm(s):
6a0121aa8b0bfc45d33ba8851fd8f796
SUSE Linux 8.2:
39cc2e905726d80d8d464ac6ef5e9147
69e919e5499e5b9db0b1a76255db03b4
2d2266d411bd668737c5f84bb6d76913
7d72a4ba37053f348d64dbcb022396ce
42abda850572e5d7e40ec7043ac3b702
source rpm(s):
ee46a20061210bf5ef2b1b70d38ec040
x86-64 Platform:
SUSE Linux 9.3:
621a2cfc18421d854254b8911ce017ed
cab0bf414148056e8fb5cf31c1befe7a
ea300b37f03dbf8f7bcec457317e0905
07fea3052e6e2ce4665f9ff718e017de
e7a6a44bdf84e3a5ba70ef41cb766182
d83a8aeedbcb74170d7126379a90292c
b0bf94e6a689bb15342c425343efa59d
df04c97479a660fde0712d7477760dfa
7a83637dde1b05cf3150ef51e6d02f7e
6e34e9eaa886d420c0ea4ba7c5e80982
d38bf84a243fe954a026c27a138f869d
71b795eb9b1a7e2767fe89edf445c299
df2ab323f0b49e00edd7a945309342b1
00908877d0c973f02ceca7789a755db8
27468621a86935d330e9d2dcfe72eef2
ff02e7c43553e4f25290f2867d53b7db
c9b1dec03a1d53398264b144a97d6dd1
source rpm(s):
3af8825e5c37e7abc754f5af9769e59f
393aa11a2f94489aa0039ed0c62115a8
SUSE Linux 9.2:
4b3167107e6eaea620548e962dafd317
f42bc2beb91160b937595ba1b88cf3c0
f66a513508c472f923a044f33ba27383
faaee204db90eb7a9a77c210769d7d75
486c409390c7190db1ff328e08893189
11621ca6c3fec8fec7458786d5f24b7f
837ec18286c150c1cfe46592a73f5726
2f46f2453ebac2b670614cab7e0aeec6
8c017cd94914bdb50ae9fb919df580a1
source rpm(s):
91258a14246da03d9e971b06d6d35a17
SUSE Linux 9.1:
d3686b16dff37c16016e104cc4e1314b
7c2ab4cd8307d316148c6539da1864bd
e8967c57a88b2ec932eb643209292078
37d1cb307e235722ef8bed4a65a6ce56
70f93f9eab72a2e5d3f6fbca1e9fa5fd
4f5142540428e3c2c753c9e7f37e6b5a
90df498c580d55093372b28b68d0438a
39a9ad1ff504dbff6f207dc35bf32bf5
0b72728104e7865c2151a77af3b6e50e
7c1cf1a1ef2f1e7658f75ab4b25da553
bdf2c7d90786f138eee5dfee5e34a117
23f2a766064c4a2824a60cb2296c8fb9
76a8d02c86e353a178f85fb83f4166a8
08b5bddde6c7ec8623ef896faf9cafd1
0df4b0a1f48f1cd2b0f8b5f45162f6a5
source rpm(s):
b431dc7a996e3174f4c21fe1055af079
SUSE Linux 9.0:
b8b80d84b0826a59afb04ad1e773ad85
60fc094836ac79534c8ea92b16761fd4
ab723621b2cfaa028452afa72d10d569
2b44fc4cdc760c035ce2e98c1a5ab405
525b88d2f48e8edc0e615f215a29effa
8819c6a665a36428eed22c1c49e2a248
source rpm(s):
4b4378269d9c74df3d618b2d168c81e5
______________________________________________________________________________
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.
====================================================================
