-----BEGIN PGP SIGNED MESSAGE-----

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                apache2
        Announcement ID:        SUSE-SA:2005:052
        Date:                   Mon, 12 Sep 2005 09:00:00 +0000
        Affected Products:      9.0, 9.1, 9.2, 9.3
                                SUSE Linux Enterprise Server 8, 9
                                Open Enterprise Server 9
        Vulnerability Type:     local command execution, authentication bypass,
                                memory consumption
        Severity (1-10):        5
        SUSE Default Package:   yes
        Cross-References:       CAN-2005-2491
                                CAN-2005-2728
                                CAN-2005-2700

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             - integer overflow in PCRE
             - memory consumption bug in byterange splitting
             - SSL client-certificate authentication bypass
           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

   PLEASE NOTE: This advisory is a re-release of SUSE-SA:2005:051 with a
   new SA ID because the ID SUSE-SA:2005:051 was already used.


   This update of apache2 fixes an integer overflow in the PCRE quantifier
   parsing which can be triggered by a local untrusted user by using a carefully
   crafted regex in a .htaccess file to execute arbitrary code. (CAN-2005-2491)

   A memory consumption bug in the byterange handling code (CAN-2005-2728)
   was fixed.

   And a flaw in mod_ssl which allows to bypass the client-certificate
   authentication in a vhost context (CAN-2005-2700) was solved.

2) Solution or Workaround

   There are no workarounds known.

3) Special Instructions and Notes

   Please restart the Apache 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.

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

    x86 Platform:

    SUSE Linux 9.3:
          a240d419004e61a3c94208bc297ffb5b
          6084268b6e5b47130846f69555485a54
          b66c2ba932bddc7d5d7b6193500f5a2b
          8cf9d900a458eaf328ad7e5475b06098
          ccd9f70705c6d171e4989140cdab73f0
    patch rpm(s):
          f67b79935f4b65789ddca57902b17786
          2c88ae4c308184d2433fa4e3c1812cde
          3579b413ec105c2de9ccf3fe45d067f7
          6f54201023745d49189cf1b32692b192
          fb7d8de4c15b248fd72649a31e48c44b
    source rpm(s):
          78e432f045b43ca1d62afd9d44d96ab0

    SUSE Linux 9.2:
          99b8339418a1e641bd2fffd7fa94ddb4
          dc24744dd9212dd9fa788cbe568369fe
          bb84d16ffa1863a3421f7c3b8770f55b
          db4a38f8922eba3be59954c311b00de7
          c5423ce0e107b1b8e4b015ffd25f5566
    patch rpm(s):
          88aa0c386dce473cf0521345a999c932
          f0683744ed767289109406441ea7e4ea
          f680997a55ec3bcdaad8694b3aa5ecbc
          1ff03c55df428f8e71c205fa600b3d7e
          036c6e06fb97ef635fb835116b33103d
    source rpm(s):
          84d688673cabbf8b319cafc019dd795b

    SUSE Linux 9.1:
          4fe736dedb51da0df880612571a4bbc0
          52df06eed158aa8b0cec885d92f103cf
          6fe17a0f1f3a770e9ae8e680e411db99
          c7ae2f36175f28a041961e8a50f4753c
          ca9f6a43373627af3cb1ddc296175ebe
    patch rpm(s):
          d02098187f6ea05bb5bdf91fbf072457
          ac3187c44fe0cae9fbd74c7b228df60a
          14838a3ea06746a4beb6a4e5f4a0a9e8
          4cb390242eb43a46532f6fdf7f0420b4
          ef53edc46eb040e7dd11356c926a8bf5
    source rpm(s):
          f7e6698966a0f65a07aade7d9e369269

    SUSE Linux 9.0:
          807308aa43e757cfdf21073d6aa137f7
          1a7af28c99748ac8b9995a3c786cd066
          78fba9bf9b95ac4627d74d15d4b155f4
          cd1e5cc7e4a0cf85cb188e49dfbccdc2
          3ea067001e1978cd0a5652d29ac1aa3d
          5b92673c9bd200792ccf57b36a76f1a5
          d1aa4577b80d7202d2873fc60d779889
    patch rpm(s):
          9a23aaf0e488b5c8edb61062d69fb425
          09e8a34d4138be61c48d61a12e9281b8
          39e0a2070d88a9edea81118250cc6bed
          f8212bfb1c488a6d53d00726e5158858
          6132f24e5a56d678550851ad7088b0b7
          cb04a0221afe61a06c302d2fdd1bb883
          51d3d131014076252bcab6744f935bcf
    source rpm(s):
          af3ad54cf46206e152eba60c9117fb0e



    x86-64 Platform:

    SUSE Linux 9.3:
          85b907f4d5a2ec7bd27497aedac4c47e
          15aa356ae44de0930c318227cb10829b
          881993b3901d83a96743057cf761c076
          783f0f9bb1cbf75883f414d4a5386fdb
          a69631d3a1e50e89203ce145f67ecb24
    patch rpm(s):
          3600699732c5033e9904667311720bb4
          06fef852a80007dace6f79c88b5a70c5
          3f6c720b867d09826e83050bfbac866b
          39d58d57fe57f00faaf9c1c1259ebb1f
          64682ae163dad142e07bc1e6ea6b136d
    source rpm(s):
          78e432f045b43ca1d62afd9d44d96ab0

    SUSE Linux 9.2:
          82797e22daf1b7e45f19f76b1bbb2f2a
          2315bf905e875d4bd18df0fea9791ed2
          7d7f9d6d2542ba689b08dd9e39d5378f
          31fb42fb5888b83a5539dad2f375dfb1
          929c857dc61df1f3923d6e4348ed8036
    patch rpm(s):
          d3583d0536314cf3c251ebb8f651270b
          b4f2c134ed3becd179429e9aee4794aa
          389ffba19d5e79f8433c06210b9b6a47
          5877685363ba342c48b6786e8006bf46
          2f40f2eb81881bd1f43246eed07cf998
    source rpm(s):
          84d688673cabbf8b319cafc019dd795b

    SUSE Linux 9.1:
          eaabd50f11cb054e1bc312e6c3c4d77c
          b01ef03e4d893483b731cf52f953b99d
          0ad003dc0ac805a939b1fd582750f24f
          4035479cecb2a8974eb5520c03bacd44
          f02d5e885195dfef2f290f0960e91da9
    patch rpm(s):
          87e46223583fad63819e12e8a7d80f7f
          2a23e71a8807111fc3007809af259786
          3f298e957f5071e0d9ea3a4fae438701
          10455ff34e03fde9dba013fbe203087e
          3aac1003eb82a13c4760742bd2831ccf
    source rpm(s):
          3b809b2754a78471090157c04b08c3e2

    SUSE Linux 9.0:
          d6b39a54ebfbdc9d5a9c9fa72b842d4c
          d2592d72f35ca1cf0d2dca098fd51b40
          f6664337bbfeba977b83097fa07b55d9
          7c804a339ee05b6282db5ac9a5cd8ac0
          9d493ef6d3ae7bd395369405efb4135d
          4afef015d327ee6e4df071e92441b0cd
          96897499420e553ba4ac97a821082530
    patch rpm(s):
          c70d2452cca409c3d46d008bbd56a444
          f91808259c4b87dfd3333360efbce9ff
          53149c85a2a09b2732986d1e548e4635
          8e6fa8a245d4e1c2e7c0f3e7003cd567
          60250857238c01c3f3524817e608fb60
          5acdeba16329ccbdefcd4d9d05284e61
          b712fd7071094be210ab0a5651c22fa2
    source rpm(s):
          3c2acceb99e8916f24d636607ae8d68e


______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Workarounds:

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