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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                apache2
        Announcement-ID:        SUSE-SA:2004:030
        Date:                   Monday, Sept  6th 15:00:00 MEST 2004
        Affected products:      8.1, 8.2, 9.0, 9.1
                                SUSE Linux Enterprise Server 9
        Vulnerability Type:     remote DoS condition
        Severity (1-10):        4
        SUSE default package:   No
        Cross References:       CAN-2004-0748
                                CAN-2004-0751

    Content of this advisory:
        1) security vulnerability resolved:
            - Remote DoS condition in mod_ssl
           problem description
        2) solution/workaround
        3) special instructions and notes
        4) package location and checksums
        5) pending vulnerabilities, solutions, workarounds:
            - mysql
            - mozilla
        6) standard appendix (further information)

______________________________________________________________________________

1) problem description, brief discussion

    The mod_ssl apache module, as part of our apache2 package, enables
    the apache webserver to handle the HTTPS protocol.
      Within the mod_ssl module, two Denial of Service conditions in the
    input filter have been found. The CVE project assigned the identifiers    CAN-2004-0748 and CAN-2004-0751 to these issues.

2) solution/workaround

    As temporary workaround you may disable the mod_ssl module in your
    apache configuration and restart the apache process without SSL
    support.

3) special instructions and notes

    As a dependency you also need to update the libapr0 package and
    one of the apache2-prefork or apache2-worker package, depending
    on whether you use the -prefork or -worker configuration.
      After successfully updating the apache2 packages, you need to
    invoke the following command as root:

      rcapache2 restart

4) package location and checksums

    Please 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 to install from the maintenance web.

    x86 Platform:

    SUSE Linux 9.1:
          433f40e694c51c51ad6feaf666d1578d
          8170358a893ba04d3b4d74e236015182
          3dc726a67d135e748f78a6000dc527d8
          66ce37d927286536ed42d2a550a11936
    patch rpm(s):
          1ece34e4984d53268e1173b17e91e86e
          4e181a7faabd372af3cb93cc89242213
          47deecc707e8f56026d04faf5319451d
          011cb36a9f642f8f824b16c2f48f8460
    source rpm(s):
          799cb084a386b1fae2a858a54496815d

    SUSE Linux 9.0:
          9716ca6d9af309014eced49e3aed1435
          cca7cde1e4686eb7d9026ccba1f40108
          e15f6a745fc06e9d945ca38330431892
          18d19ab4d95d5207916be196955e7652
    patch rpm(s):
          35cdf8ad985b99cded759d4ccb890599
          fd3c69cf2ff5909e1655c91510b2d1e4
          734c25b846c67bd3f58025c365840ba3
          dc449507540ffcdd74f9a48fa0405e1b
    source rpm(s):
          fcf7553527ed40711a9be974387cd2e7

    SUSE Linux 8.2:
          2e1e2c708ef7de99d0b525fff3f74f1a
          494abba563e196250ada05b5cc9175de
          1f3ac2985560172e302fb2f59342219a
          4430ea5520fc4c2f508f85deb91aa55f
    patch rpm(s):
          3da30ffcdfc6553bcf48a760a44504d9
          c8c96e0d447159257f0cf1a2c1c67e8e
          5a055bbd7c1c79d3000e0ce8476012a1
          bbb4ccd8d45e9e780e66910193b3f308
    source rpm(s):
          7fcc077468056c757dee017c6bcaffcb

    SUSE Linux 8.1:
          13f7ab88c2964d95eb0825e984cbb0d3
          1cff4b7af7981a59d2988de06ac688c5
          2d5bdacb78558398ab507871937c8f90
    patch rpm(s):
          903c44cb7d53f0a165e9387945f974a7
          8ec2a1b9e30a461dcc9a8777402d52e1
          b08f5bdcc3f58db67d32a344d3902976
    source rpm(s):
          5b00953279e7a3f3441d3aca913993d2



    x86-64 Platform:

    SUSE Linux 9.1:
          2ead08c048c3679dab9453d75cef840b
          757c0c5fdbbb7e99ffe47d93d3332d90
          554a35e7c3d0bb3443b6169ce6452353
          7b6e73a8d78be1bb641827b8a8281001
    patch rpm(s):
          a3531dc3e3ee938328590ef3867e41c8
          712c92887c067f6371acba5b9c5a9666
          03f0a37427a40b9b28a1f76cb9bf4625
          a9d56bd73b0860ac07b829646d6c9f46
    source rpm(s):
          1257782dc5ab84638be2e6eaeb0658ba

    SUSE Linux 9.0:
          6d00b07c2577f46d2b464502b6154dcd
          84c0a4413d6a7f8058db619c62f27f56
          a1751a0d1555bb673caabb2dc9ffd737
          e518ef9af6f35353ee1ae6d7ae46c6c6
    patch rpm(s):
          6385344c519e3eaea57b70e14e9cab03
          3377fb1e2544b5b770d0b815a4aebae7
          b1787747e3d635f641d21c2c65f22121
          867a3e682a3e3c370937af16042dd1f6
    source rpm(s):
          4655bf3ac1bc8853957c84a15471edbc

______________________________________________________________________________

5)  Pending vulnerabilities in SUSE Distributions and Workarounds:

    - mysql
    New mysql packages are available on our ftp servers, fixing a tmp
    race condition in the mysqlhotcopy script.

    - mozilla
    We are in the process of releasing updates for mozilla (and related
    browsers), fixing various issues: CAN-2004-0597, CAN-2004-0718,
    CAN-2004-0722, CAN-2004-0757, CAN-2004-0758, CAN-2004-0759, CAN-2004-0760,
    CAN-2004-0761, CAN-2004-0762, CAN-2004-0763, CAN-2004-0764 and
    CAN-2004-0765.
    We will give you concrete details in a separate mozilla advisory when the
    updates are available.

______________________________________________________________________________

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 
       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 disrecommend to subscribe to security lists which cause the
       email 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 
       to verify the signature of the package, where  is the
       filename of the rpm package that you have downloaded. Of course,
       package authenticity verification can only target an un-installed 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  .


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

    For general information or the frequently asked questions (faq) 
    send mail to:
         or
         respectively.

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================

SuSE: 2004-030: apache2 Security Update

September 6, 2004
The mod_ssl apache module, as part of our apache2 package, enables The mod_ssl apache module, as part of our apache2 package, enables the apache webserver to handle the HTTPS pr...

Summary


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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                apache2
        Announcement-ID:        SUSE-SA:2004:030
        Date:                   Monday, Sept  6th 15:00:00 MEST 2004
        Affected products:      8.1, 8.2, 9.0, 9.1
                                SUSE Linux Enterprise Server 9
        Vulnerability Type:     remote DoS condition
        Severity (1-10):        4
        SUSE default package:   No
        Cross References:       CAN-2004-0748
                                CAN-2004-0751

    Content of this advisory:
        1) security vulnerability resolved:
            - Remote DoS condition in mod_ssl
           problem description
        2) solution/workaround
        3) special instructions and notes
        4) package location and checksums
        5) pending vulnerabilities, solutions, workarounds:
            - mysql
            - mozilla
        6) standard appendix (further information)

______________________________________________________________________________

1) problem description, brief discussion

    The mod_ssl apache module, as part of our apache2 package, enables
    the apache webserver to handle the HTTPS protocol.
      Within the mod_ssl module, two Denial of Service conditions in the
    input filter have been found. The CVE project assigned the identifiers    CAN-2004-0748 and CAN-2004-0751 to these issues.

2) solution/workaround

    As temporary workaround you may disable the mod_ssl module in your
    apache configuration and restart the apache process without SSL
    support.

3) special instructions and notes

    As a dependency you also need to update the libapr0 package and
    one of the apache2-prefork or apache2-worker package, depending
    on whether you use the -prefork or -worker configuration.
      After successfully updating the apache2 packages, you need to
    invoke the following command as root:

      rcapache2 restart

4) package location and checksums

    Please 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 to install from the maintenance web.

    x86 Platform:

    SUSE Linux 9.1:
          433f40e694c51c51ad6feaf666d1578d
          8170358a893ba04d3b4d74e236015182
          3dc726a67d135e748f78a6000dc527d8
          66ce37d927286536ed42d2a550a11936
    patch rpm(s):
          1ece34e4984d53268e1173b17e91e86e
          4e181a7faabd372af3cb93cc89242213
          47deecc707e8f56026d04faf5319451d
          011cb36a9f642f8f824b16c2f48f8460
    source rpm(s):
          799cb084a386b1fae2a858a54496815d

    SUSE Linux 9.0:
          9716ca6d9af309014eced49e3aed1435
          cca7cde1e4686eb7d9026ccba1f40108
          e15f6a745fc06e9d945ca38330431892
          18d19ab4d95d5207916be196955e7652
    patch rpm(s):
          35cdf8ad985b99cded759d4ccb890599
          fd3c69cf2ff5909e1655c91510b2d1e4
          734c25b846c67bd3f58025c365840ba3
          dc449507540ffcdd74f9a48fa0405e1b
    source rpm(s):
          fcf7553527ed40711a9be974387cd2e7

    SUSE Linux 8.2:
          2e1e2c708ef7de99d0b525fff3f74f1a
          494abba563e196250ada05b5cc9175de
          1f3ac2985560172e302fb2f59342219a
          4430ea5520fc4c2f508f85deb91aa55f
    patch rpm(s):
          3da30ffcdfc6553bcf48a760a44504d9
          c8c96e0d447159257f0cf1a2c1c67e8e
          5a055bbd7c1c79d3000e0ce8476012a1
          bbb4ccd8d45e9e780e66910193b3f308
    source rpm(s):
          7fcc077468056c757dee017c6bcaffcb

    SUSE Linux 8.1:
          13f7ab88c2964d95eb0825e984cbb0d3
          1cff4b7af7981a59d2988de06ac688c5
          2d5bdacb78558398ab507871937c8f90
    patch rpm(s):
          903c44cb7d53f0a165e9387945f974a7
          8ec2a1b9e30a461dcc9a8777402d52e1
          b08f5bdcc3f58db67d32a344d3902976
    source rpm(s):
          5b00953279e7a3f3441d3aca913993d2



    x86-64 Platform:

    SUSE Linux 9.1:
          2ead08c048c3679dab9453d75cef840b
          757c0c5fdbbb7e99ffe47d93d3332d90
          554a35e7c3d0bb3443b6169ce6452353
          7b6e73a8d78be1bb641827b8a8281001
    patch rpm(s):
          a3531dc3e3ee938328590ef3867e41c8
          712c92887c067f6371acba5b9c5a9666
          03f0a37427a40b9b28a1f76cb9bf4625
          a9d56bd73b0860ac07b829646d6c9f46
    source rpm(s):
          1257782dc5ab84638be2e6eaeb0658ba

    SUSE Linux 9.0:
          6d00b07c2577f46d2b464502b6154dcd
          84c0a4413d6a7f8058db619c62f27f56
          a1751a0d1555bb673caabb2dc9ffd737
          e518ef9af6f35353ee1ae6d7ae46c6c6
    patch rpm(s):
          6385344c519e3eaea57b70e14e9cab03
          3377fb1e2544b5b770d0b815a4aebae7
          b1787747e3d635f641d21c2c65f22121
          867a3e682a3e3c370937af16042dd1f6
    source rpm(s):
          4655bf3ac1bc8853957c84a15471edbc

______________________________________________________________________________

5)  Pending vulnerabilities in SUSE Distributions and Workarounds:

    - mysql
    New mysql packages are available on our ftp servers, fixing a tmp
    race condition in the mysqlhotcopy script.

    - mozilla
    We are in the process of releasing updates for mozilla (and related
    browsers), fixing various issues: CAN-2004-0597, CAN-2004-0718,
    CAN-2004-0722, CAN-2004-0757, CAN-2004-0758, CAN-2004-0759, CAN-2004-0760,
    CAN-2004-0761, CAN-2004-0762, CAN-2004-0763, CAN-2004-0764 and
    CAN-2004-0765.
    We will give you concrete details in a separate mozilla advisory when the
    updates are available.

______________________________________________________________________________

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 
       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 disrecommend to subscribe to security lists which cause the
       email 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 
       to verify the signature of the package, where  is the
       filename of the rpm package that you have downloaded. Of course,
       package authenticity verification can only target an un-installed 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  .


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

    For general information or the frequently asked questions (faq) 
    send mail to:
         or
         respectively.

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================

References

Severity

Related News