=====================================================================
                                  CERT-Renater

                       Note d'Information No. 2005/VULN040
_____________________________________________________________________

DATE                      : 18/01/2005

HARDWARE PLATFORM(S)      : /

OPERATING SYSTEM(S)       : Systems running php4, mod_php4.

======================================================================

______________________________________________________________________________

                         SUSE Security Announcement

         Package:                php4, mod_php4
         Announcement-ID:        SUSE-SA:2005:002
         Date:                   Monday, Jan 17th 2005 18:00 MEST
         Affected products:      8.1, 8.2, 9.0, 9.1, 9.2
                                 SUSE Linux Enterprise Server 8, 9
         Vulnerability Type:     remote code execution
         Severity (1-10):        7
         SUSE default package:   no
         Cross References:       CAN-2004-1019
                                 CAN-2004-1065
                                 http://bugs.php.net/bug.php?id=25753

     Content of this advisory:
         1) security vulnerability resolved:
              - buffer overflows in PHP
              - PHP source code disclosure
            problem description
         2) solution/workaround
         3) special instructions and notes
         4) package location and checksums
         5) pending vulnerabilities, solutions, workarounds:
         6) standard appendix (further information)

______________________________________________________________________________

1) problem description, brief discussion

     PHP is a well known, widely-used scripting language often used within web
     server setups.

     Stefan Esser and Marcus Boerger found several buffer overflow problems in
     the unserializer functions of PHP (CAN-2004-1019) and Ilia Alshanetsky
     (CAN-2004-1065) found one in the exif parser. Any of them could allow
     remote attackers to execute arbitrary code as the user running the PHP
     interpreter.

     Additionally a bug where the server would disclose php sourcecode under
     some circumstances has been fixed.

2) solution/workaround

     There is no workaround known besides disabling PHP. Therefore we recommend
     to install the updated packages.

3) special instructions and notes

     If you use php as module within apache you have to restart the server by
     executing the following command as root:

          /usr/sbin/rcapache restart

     or if you use the apache2 server

          /usr/sbin/rcapache2 restart

4) package location and checksums

     Download the update package for your distribution and verify its
     integrity by the methods listed in section 3) of this announcement.
     Then, install the package using the command "rpm -Fhv file.rpm" to apply
     the update.
     Our maintenance customers are being notified individually. The packages
     are being offered for installation from the maintenance web.

     x86 Platform:

     SUSE Linux 9.2:
     ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/php4-4.3.8-8.3.i586.rpm
       e871c76bb7c0ba1fc34268e05ee54e94
     ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/apache2-mod_php4-4.3.8-8.3.i586.rpm
       e9e0e5cbfa8805b6a5866cd91db1e715
     patch rpm(s):
     ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/php4-4.3.8-8.3.i586.patch.rpm
       7bc595dd946b7287c1b590283526500b
     ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/i586/apache2-mod_php4-4.3.8-8.3.i586.patch.rpm
       e72c58f0d9fbb9d7b0e23251f50b22c5
     source rpm(s):
     ftp://ftp.suse.com/pub/suse/i386/update/9.2/rpm/src/php4-4.3.8-8.3.src.rpm
       e80aff98a2d6bdcb56bf6ed7e1731611

     SUSE Linux 9.1:
     ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/php4-4.3.4-43.22.i586.rpm
       01ddb36914f644c65165250b7c7689e8
     ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/apache2-mod_php4-4.3.4-43.22.i586.rpm
       9a3db7a8dcc0e5d6b49911d25e755069
     ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/mod_php4-core-4.3.4-43.22.i586.rpm
       c072a97d0081976292d4d5005019dccd
     patch rpm(s):
     ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/php4-4.3.4-43.22.i586.patch.rpm
       01853c982ea0c89faecfe3fb568313b6
     ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/apache2-mod_php4-4.3.4-43.22.i586.patch.rpm
       dd64ede42cf3a31a99df2e90ebb597a1
     ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/i586/mod_php4-core-4.3.4-43.22.i586.patch.rpm
       d499fac997192f14e949398df2624a9d
     source rpm(s):
     ftp://ftp.suse.com/pub/suse/i386/update/9.1/rpm/src/php4-4.3.4-43.22.src.rpm
       7f23c05761153fec8786c9261e60a49a

     SUSE Linux 9.0:
     ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/mod_php4-4.3.3-183.i586.rpm
       bbf8be6995d2590af1e2a5d12d101ba6
     ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/apache2-mod_php4-4.3.3-183.i586.rpm
       d8c08e3e05104d0a291cc1b98111c3a1
     ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/mod_php4-core-4.3.3-183.i586.rpm
       cb01290bc7c2b968eacea15114033ad4
     patch rpm(s):
     ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/mod_php4-4.3.3-183.i586.patch.rpm
       d69e6d3885258f06059f0c8cc4b3fc95
     ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/apache2-mod_php4-4.3.3-183.i586.patch.rpm
       1d8029716edec5d69b9e9f54d2b311df
     ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/i586/mod_php4-core-4.3.3-183.i586.patch.rpm
       a9d2199cb9d2ddb904a723d0a6107300
     source rpm(s):
     ftp://ftp.suse.com/pub/suse/i386/update/9.0/rpm/src/mod_php4-4.3.3-183.src.rpm
       59f6c6664cad5ded05ce4b22d856d496

     SUSE Linux 8.2:
     ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mod_php4-4.3.1-174.i586.rpm
       5a477c5733f83b776f746bc3431d8207
     ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/apache2-mod_php4-4.3.1-174.i586.rpm
       90eb5f5d40142d7d34a3b46c5ce87ac8
     ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mod_php4-core-4.3.1-174.i586.rpm
       f55cf3b586c8a921700e8ecfb8ad5941
     patch rpm(s):
     ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mod_php4-4.3.1-174.i586.patch.rpm
       e6c583ddaa03bd85729c46d9ddfc75dd
     ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/apache2-mod_php4-4.3.1-174.i586.patch.rpm
       3053986191c3dd2354b931ea31fc9208
     ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/mod_php4-core-4.3.1-174.i586.patch.rpm
       7a8d67f1e02ea516f21df3ad69107b00
     source rpm(s):
     ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/mod_php4-4.3.1-174.src.rpm
       1d709df9d796d6f723590bc31afe9b18

     SUSE Linux 8.1:
     ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mod_php4-4.2.2-485.i586.rpm
       f597d7af4c5c3eb3fa74ead654ac79e3
     ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mod_php4-core-4.2.2-485.i586.rpm
       136007f47679877b999eeee170bc0003
     patch rpm(s):
     ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mod_php4-4.2.2-485.i586.patch.rpm
       07b674f1ec878bbb6ee68e6da52144d4
     ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/mod_php4-core-4.2.2-485.i586.patch.rpm
       30c83209b3e7177f9ac34365f51f9c72
     source rpm(s):
     ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/mod_php4-4.2.2-485.src.rpm
       e6a23b4c8cbba800d002104da80fbc17



     x86-64 Platform:

     SUSE Linux 9.2:
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/php4-4.3.8-8.3.x86_64.rpm
       96c10340cd1e9dbd499ceb264ff6862b
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/x86_64/apache2-mod_php4-4.3.8-8.3.x86_64.rpm
       0650c7390f4b341ad496030e6d7c7585
     source rpm(s):
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.2/rpm/src/php4-4.3.8-8.3.src.rpm
       e80aff98a2d6bdcb56bf6ed7e1731611

     SUSE Linux 9.1:
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/php4-4.3.4-43.22.x86_64.rpm
       d7b5bd55bd381bbf674ad9111e336741
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/apache2-mod_php4-4.3.4-43.22.x86_64.rpm
       0b8d4a5de7c53fef7364ef2883269c95
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/mod_php4-core-4.3.4-43.22.x86_64.rpm
       f973f7d09700571dca8221aaffa8a74b
     patch rpm(s):
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/php4-4.3.4-43.22.x86_64.patch.rpm
       cf568e895d1b4e79ba0a87c3ddfa68fe
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/apache2-mod_php4-4.3.4-43.22.x86_64.patch.rpm
       d74c95e6d64ab16ebd8b0bfc1bfda08f
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/x86_64/mod_php4-core-4.3.4-43.22.x86_64.patch.rpm
       12c7794749389feaec02b707da12c4d4
     source rpm(s):
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.1/rpm/src/php4-4.3.4-43.22.src.rpm
       61ae620d5e5bb9c6ebb53c77fdd2f0ee

     SUSE Linux 9.0:
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/mod_php4-4.3.3-183.x86_64.rpm
       42ddc755c8a14eda9a2e7527e1c6ab83
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/apache2-mod_php4-4.3.3-183.x86_64.rpm
       96cf0ad7d9dd5faed47a81619a3f11e9
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/mod_php4-core-4.3.3-183.x86_64.rpm
       a4af66488b211562da363b342c80fabd
     patch rpm(s):
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/mod_php4-4.3.3-183.x86_64.patch.rpm
       564fc4425ba3d8c995836b61c93082f9
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/apache2-mod_php4-4.3.3-183.x86_64.patch.rpm
       67580deaea8aed5c1f6af1c8fb5f7889
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/x86_64/mod_php4-core-4.3.3-183.x86_64.patch.rpm
       bfe305060c4ca74d88b8503996a953ae
     source rpm(s):
     ftp://ftp.suse.com/pub/suse/x86_64/update/9.0/rpm/src/mod_php4-4.3.3-183.src.rpm
       e1f76b408a70416b1e80dd2fb8f6721a

______________________________________________________________________________

5) Pending vulnerabilities in SUSE Distributions and Workarounds:

     Please read our weekly summary report for more information.

______________________________________________________________________________

6) standard appendix: authenticity verification, additional information

   - Package authenticity verification:

     SUSE update packages are available on many mirror ftp servers all over
     the world. While this service is being considered valuable and important
     to the free and open source software community, many users wish to be
     sure about the origin of the package and its content before installing
     the package. 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) md5sums as provided in the (cryptographically signed) announcement.
     2) using the internal gpg signatures of the rpm package.

     1) execute the command
         md5sum <name-of-the-file.rpm>
        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
        announcement. Since the announcement containing the checksums is
        cryptographically signed (usually using the key security@suse.de),
        the checksums show proof of the authenticity of the package.
        We recommend against subscribing to security lists that cause the
        e-mail message containing the announcement to be modified
        so that the signature does not match after transport through the mailing
        list software.
        Downsides: You must be able to verify the authenticity of the
        announcement in the first place. If RPM packages are being rebuilt
        and a new version of a package is published on the ftp server, all
        md5 sums for the files are useless.

     2) rpm package signatures provide an easy way to verify the authenticity
        of an rpm package. Use the command
         rpm -v --checksig <file.rpm>
        to verify the signature of the package, where <file.rpm> is the
        file name of the rpm package that you have downloaded. Of course,
        package authenticity verification can only target an uninstalled rpm
        package file.
        Prerequisites:
         a) gpg is installed
         b) The package is signed using a certain key. The public part of this
            key must be installed by the gpg program in the directory
            ~/.gnupg/ under the user's home directory who performs the
            signature verification (usually root). You can import the key
            that is used by SUSE in rpm packages for SUSE Linux by saving
            this announcement to a file ("announcement.txt") and
            running the command (do "su -" to be root):
             gpg --batch; gpg < announcement.txt | gpg --import
            SUSE Linux distributions version 7.1 and thereafter install the
            key "build@suse.de" upon installation or upgrade, provided that
            the package gpg is installed. The file containing the public key
            is placed at the top-level directory of the first CD (pubring.gpg)
            and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .


   - SUSE runs two security mailing lists to which any interested party may
     subscribe:

     suse-security@suse.com
         -   general/linux/SUSE security discussion.
             All SUSE security announcements are sent to this list.
             To subscribe, send an email to
                 <suse-security-subscribe@suse.com>.

     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 email to
                 <suse-security-announce-subscribe@suse.com>.

     For general information or the frequently asked questions (faq)
     send mail to:
         <suse-security-info@suse.com> or
         <suse-security-faq@suse.com> respectively.

     =====================================================================
     SUSE's security contact is <security@suse.com> or <security@suse.de>.
     The <security@suse.de> public key is listed below.
     =====================================================================
______________________________________________________________________________

     The information in this advisory may be distributed or reproduced,
     provided that the advisory is not modified in any way. In particular,
     it is desired that the clear-text signature shows proof of the
     authenticity of the text.
     SUSE Linux AG makes no warranties of any kind whatsoever with respect
     to the information contained in this security advisory.

Type Bits/KeyID    Date       User ID
pub  2048R/3D25D3D9 1999-03-06 SuSE Security Team <security@suse.de>
pub  1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>

======================================================================

         =========================================================
         Les serveurs de référence du CERT-Renater
         http://www.urec.fr/securite
         http://www.cru.fr/securite
         http://www.renater.fr
         =========================================================
         + CERT-RENATER          | tel : 01-53-94-20-44          +
         + 151 bd de l'Hopital   | fax : 01-53-94-20-41          +
         + 75013 Paris           | email: certsvp@renater.fr     +
         =========================================================








