-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                php4,php5
        Announcement ID:        SUSE-SA:2005:051
        Date:                   Mon, 05 Sep 2005 10:00:00 +0000
        Affected Products:      9.0, 9.1, 9.2, 9.3
                                SUSE Linux Enterprise Server 8, 9
        Vulnerability Type:     remote code execution
        Severity (1-10):        8
        SUSE Default Package:   yes
        Cross-References:       CAN-2005-2491
                                CAN-2005-1921
                                CAN-2005-2498

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             XML_RPC problems and PCRE integer overflows
           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

   This update fixes the following security issues in the PHP scripting
   language.

   - Bugs in the PEAR::XML_RPC library allowed remote attackers to pass
     arbitrary PHP code to the eval() function (CAN-2005-1921,
     CAN-2005-2498).

     The Pear::XML_RPC library is not used by default in SUSE Linux, but
     might be used by third-party PHP applications.

   - An integer overflow bug was found in the PCRE (perl compatible regular
     expression) library which could be used by an attacker to potentially
     execute code. (CAN-2005-2491)

   Please note:
   This is a reissue of the previous PHP update (SUSE-SA:2005:049)
   which due to a mixup between PCRE version was causing breakage in
   nearly all PHP applications.

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 and Apache2 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.

   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web.


   x86 Platform:

   SUSE Linux 9.3:
             4e90acc88222e0cfdd07b6072879a01c
             9b720ec166dd743b28a36af39f80787b
             6ad0aeb47ca68ce05bc791aa23b79c88
             1504b1d434393bf8063f4f3437494413
             92a7d868a14f8213e98d2156f8b03896
             c31a4e4411ba874af1abe582951b4ab3
             5efa0c90e7def9703a4c966d2e0900bf
             9ec97253dad41195bf54e53a1e7bffe9
             4ffe6e672b776a2f04043b80e84588c3
             c9acb5d272ff11abce969eb58533ec52
             e99f25e2fe0bdad0d3a8fbaab5f2b6de
             5e41e698ac494cc15665158871521f16
             1a1efc73e712ab7ac8c7397ab678c994
             0d26964958230ac0518d96480ea5d3ac
             6719612d44d37a02d326165656ab85ff
             801d88b5b132a117dbfa9dbb49c2b144
             ba7e44d7dec841fd1a5b072c68b1d853
             f6fca65a78069c259bcdf0a9f42a2876

   SUSE Linux 9.2:
             46c997462ac9747513971ca7a1f72038
             fafcc24f2c01c3411db03290891b9909
             64e246873a3c635d493f8733129a261f
             bd1449bd4ac8f78896b550faa33aec6d
             3003a2e367fa23a173be495686582197
             d86a2f9d18055e66d905d03d58b9bf35
             62920f58daea0f34845c3b3686c60f29
             e79e178f92b4a8fc870dc56e6cc4d586
             c00cd9d53e3b0f6cf177d56b74bf72ee
             f0ee8f3efe97797a10141478ea56762e

   SUSE Linux 9.1:
             3037b89a7af03ca1395bca7e88bbc54b
             36d0a8797195cbfd4d14b4b65eb7c6f2
             0ca2424d6bf16a7db69cea87b587802c
             20f242b957c4d44f91f7a04fa547fd56
             bf5a148d884ba3436e82c287d3af748d
             86177c5bf27a93d1c4e3022645a92f19
             f267a890df6c2313c2ea4a0c34f16ab9
             adfc4be6ef3a7a9a16551eaeadbff29b
             f0ac80fb83eebf6d5faaa5652b8f53b7
             28be389666538eec751a76a15f1295c7
             ad1ea41171562ed55fe2b2fdab858d91
             e067adec39ca98f3d36c6643853fef8d
             df1b436009cce77c3a93c757f31d7922
             8290e526a3faf5fcdd6109e2e1caf0b0
             b290de77f6fe768f343cdaa78634e0a0
   source rpm(s):
             da3468926b7122f748b6d9650facb3c8

   SUSE Linux 9.0:
             cec496652002d4b9839c8cd3e52bda1e
             fe0ccb1c242ab8ecd0c5ffdba6d44d01
             de914c91c71dc3ea4ed5135953c7d207
             0403f1160cbe921ec5b869cfed69e50c
             88eb0ade1823c4d6a80eaf67b7a58122
             d04d4a10dd24daa91319cfee8f848701
   source rpm(s):
             78c7187256423753cc7c61047f3f50d8

   x86-64 Platform:

   SUSE Linux 9.3:
             a556b45bcd3aa69b0042579f0e81d0e1
             bfb3a4d06a26dc5bb72d8649c457c443
             6fab6f38e5ff84b03a5ed58eb5d3fa10
             aa8884d5999c87d7d8ebea19f15ca202
             120e3bbb355440d0358a3d517d7842f3
             d5b9bd419eff80d2746028e17617e921
             6b1009e7088804e085175e1d437bf639
             41e5b63b1be10024629ffc8ef3ac6d14
             19b2730fe48c50b7e2e248ba97bee302
             14528e482fccec7efee5d66da3a36984
             307db1d3d6d1fb62bec9be76d72bf5c9
             087716be6900c151af1e5b210987c67c
             4605a056bde54010680fa5ed2aa96a11
             e245ac9ae2c25f1b9158abf4342114b4
             85f3eec0f843f590429596fb36435a2a
             8787a3c3f47f3b031ee0a6d324c3a001
             254e17db032e7e5ab576343744c5da5b
   source rpm(s):
             75c4c61d9b299430a7f27dfd18c7ce66
             3b2ca7fe5b48298d2d3f17eef2391a6a

   SUSE Linux 9.2:
             1441b3484cfa8c57a4648ad61c00b10d
             e83b4733bb349975ff7b74a01f4dcf62
             4ae26534364961bba19bd3b8ab8ec70a
             b48c91b9167d335b2100c58e3f593ca4
             0b74a18c49e1718a386fba602ca10c41
             57aa8020f196239b9492b02a607398ea
             e83b1e1bd5d4334b3d0825bd2e0a0afe
             d111c73c620463165a3858c858b5dabb
             1be9f88340a3c23141d02ad57bb3ed43
   source rpm(s):
             8dd6bb18c0386edaea9790a3671e8fd2

   SUSE Linux 9.1:
             0be147f8a17c8c776e97b2278b061816
             0f44467b5e41ff81a69081fa0ae2ea51
             d2a13d33f13834f684ef07a229a31c6c
             4138b87d59ab493f77398662b9140417
             4131b4316b73168df45a2e1a365bdfb8
             1c47381d729ef9a49eff859a696b692b
             bf87ab14a2e0e0f564f446985e29ccb6
             c5c1cd2ec835f66417578ebfad0e5818
             688ca964d613cdc2c5d95d3b4c42ec2d
             e0bafc0cbb4f5f80952fc0ac4a1f3d0c
             5086d6e8c5d0ed172c6106cc0c006ee0
             222126d57ccc9c433786167012de8fac
             f92bd9ca8095d02771425e229669670f
             2e131360c5da890defc7a755bb29c278
             a11878d347a06392924116cabf5b73ff
   source rpm(s):
             bba3ce97ae17dd7a74c46e9968edd79a

   SUSE Linux 9.0:
             4d11fd42bbf56c6e8926cfc8c98309fa
             4ed077607cd5e38f6d446353ca0732c8
             9f3eeef7c577478c290fc453362240af
             8d191c8d9696573755f8926a44b49bf5
             32f2a745cad34cfc569ce5c17e02ff76
             a864ce932e3bfc5aeec95fbd2267cd77
   source rpm(s):
             dd9e0d81f19873a12755ce2a488d45ca


______________________________________________________________________________

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.
    ====================================================================