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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                apache,apache2
        Announcement ID:        SUSE-SA:2005:046
        Date:                   Tue, 16 Aug 2005 07:00:00 +0000
        Affected Products:      8.2, 9.0, 9.1, 9.2, 9.3
                                SUSE Linux Enterprise Server 8, 9
        Vulnerability Type:     authentication bypass
        Severity (1-10):        6
        SUSE Default Package:   no
        Cross-References:       CAN-2005-2088
                                CAN-2005-1268


    Content of This Advisory:
        1) Security Vulnerability Resolved:
             apache and apache2 request smuggling
           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 security flaw was found in the Apache and Apache2 web servers which
   allows remote attacker to "smuggle" requests past filters by providing
   handcrafted header entries.

   Fixed Apache 2 server packages were released on July 26th,
   fixed Apache 1 server packages were released on August 15th.

   This issue is tracked by the Mitre CVE ID CAN-2005-2088.

   The Apache2 packages additionally fix a single byte overflow in the SSL
   CRL handling functionality, tracked by the Mitre CVE ID CAN-2005-1268.

   The Apache1 packages additionally fix a harmless local buffer overflow
   in htpasswd.

2) Solution or Work-Around

   None, please install the updated packages.

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:
             f139e14297b5e62c297bdeeb91a72cfb
             f3b91a27ce46603221423ce450f64b91
             8085487fab1bd301013e4f4268cd5515

   SUSE Linux 9.2:
             3bcb58b4cfb08896be787bb62328197c
             1e520e3c81f6b7ec84bb4127f9c0ec52
             ff8b691c1d44e33ef43f46f0bd2e9016

   SUSE Linux 9.1:
             5bc20e44e197e7b9af2d26984c511950
             ec6a62ab160adebecbf5800fb0bde028
             dfee5fdccd1fba307a0e580d08920114
             6ba6fde3121ce95efed896b55b3616b4
             825ff943742470dcf2deb459094dfc77
             cab6bc047c236ca9c19445103bf2b08a
             df114a68dc94134f1f78266c8a9b4162
   source rpm(s):
             64a3415d384bae98734bfb029a0bfd74

   SUSE Linux 9.0:
             3ea2571ee8b8f7533cfa19254ce76000
             e79c7b6cd99c86101dbae77d66a355b7
             59f010b8e181975da80ea656104f7a1e
             65969fcd4b69912398b0ac133995dd6c
             39efd1a9f7bf2693021642ef5d5f8fba
             1fe7b5b73f73a747d1290bc495432a50
             da0a791f90e62f5ab3f49a52b7ad037b
             0fdf9b7ab16b03354ee17b305b6e46a5
             d1a4d5a06d9ca6b64ee6c7d0fe2ef434
             8d2f2b1d0e058fd51fa211adb997815c
             241b06b75109f29623e48355a22e5cc5
   source rpm(s):
             34ce607ad6ce1cd5ce400540ff0fc5c8
             5b4e779401060cdef792aec5a83e298d

   SUSE Linux 8.2:
             3a3ce9aaf22ef266e4465dd845540103
             891f721003c52433a230d88b6a674740
             9c91e87e0c4305a006c041ab56c5bb4a
             a95d8a3e01285ab512e67ff99544e738
             830692c995bf913b308ef992b122d8d3
             c9f022344948a3af810e0f706003b605
             6c23c596575d6dc4e4c5ed8484b96bc5
             0a9dcbdfcbf4b862b8b2da9970032ad3
   source rpm(s):
             8ed1800dc6ae23fdde92aeaab8467277

   x86-64 Platform:

   SUSE Linux 9.3:
             b0191eba7fbb1bc9f9c154b48f19f41e
             feec5b490afdbd30249923ccf791e5e1
             418f4b6310bb98177b477a8c2af0fd3e
   source rpm(s):
             51cd4351f98f32df47c5d15beeeb055c

   SUSE Linux 9.2:
             2a5421e418e43d552a4782d3bc9a2486
             1617072b6ebfe834251e8e6084acf71b
             a0ee7a530aefc0c902b45ffc5f140758
   source rpm(s):
             038265691d3d304c63301d1900d9c8f5

   SUSE Linux 9.1:
             8d5268bb9772648aea84ab6c96f729e5
             cd24e073b85c1ad2ae0f4f9ac7f03833
             aa96fe4043dadd434bfdbbcbda5b9e3c
             fdef881a458ce47c4ab3852bc03b03c3
             4949d1b12846fc5ba998ba828f1d3aa2
             db46554809bdcdb0d680f950a37d1a67
             cd742baacc51deb46e77abf44ee7852b
   source rpm(s):
             2bf68594e45e71944ae666b9d05f042d

   SUSE Linux 9.0:
             383bb73f15037bdf193b43e8356c24e2
             5a91de1118c01e36103bed561afaf461
             0fe7ab322847c94c8346f259ab666973
             e02b174d4b8312c9370d04e531c6cb6f
             5cbf2baf68a56df0e95149a209dcc5bb
             0512d0806364982cb77e300807f0c2ab
             66e024c176e86ae70f9cce5f68bbbb6e
             42046fedac25e435a87048895ba892a3
             2cf1c65663e16108cb25300e171a195b
             87b741b0402f03064de4619dff361086
             09458018034cfffbc419d816c5dd31ce
   source rpm(s):
             ae182ca0cb6e47559f250feca8c67e2e
             e87c50cda40a5c9097bab2e20c1098d6


______________________________________________________________________________

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