SUSE: 2006-063 Moderate: OpenSSH Remote Attack Denial Of Service

Warning: Undefined array key "advisoryid" in /var/www/www.linuxsecurity.com-443/html/tmp/regularlabs/custom_php/3700665_1edcd913e2b52798c5b9126b8927230e on line 19

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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                openssh
        Announcement ID:        SUSE-SA:2006:062
        Date:                   Fri, 20 Oct 2006 17:00:00 +0000
        Affected Products:      Novell Linux Desktop 9
                                Novell Linux POS 9
                                Open Enterprise Server
                                SUSE LINUX 10.1
                                SUSE LINUX 10.0
                                SUSE LINUX 9.3
                                SUSE LINUX 9.2
                                SuSE Linux Desktop 1.0
                                SuSE Linux Enterprise Server 8
                                SuSE Linux Openexchange Server 4
                                SUSE LINUX Retail Solution 8
                                SuSE Linux School Server
                                SuSE Linux Standard Server 8
                                SUSE SLED 10
                                SUSE SLES 10
                                SUSE SLES 9
                                UnitedLinux 1.0
        Vulnerability Type:     remote denial of service
        Severity (1-10):        7
        SUSE Default Package:   yes
        Cross-References:       CVE-2006-4924, CVE-2006-4925, CVE-2006-5051
                                CVE-2006-5052

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             various openssh security problems fixed in openssh 4.4
           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

   Several security problems were fixed in OpenSSH 4.4 and the bug fixes were
   back ported to the openssh versions in our products.

   - CVE-2006-4924: A denial of service problem has been fixed in OpenSSH which could
     be used to cause lots of CPU consumption on a remote openssh server.

   - CVE-2006-4925: If a remote attacker is able to inject network traffic this could
     be used to cause a client connection to close.

   - CVE-2006-5051: Fixed an unsafe signal handler reported by Mark Dowd. The signal
     handler was vulnerable to a race condition that could be exploited to perform a
     pre-authentication denial of service. This vulnerability could theoretically lead to
     pre-authentication remote code execution if GSSAPI authentication is enabled,
     but the likelihood of successful exploitation appears remote.

   - CVE-2006-5052: Fixed a GSSAPI authentication abort that could be used to determine
     the validity of user names on some platforms.


2) Solution or Work-Around

   There is no known workaround, please install the update packages.

3) Special Instructions and Notes

   On SUSE Linux Enterprise Server 8, please close and restart the sshd service after
   installing this update.

   All other products do this automatically during installation, there
   is no action necessary.

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.


   x86 Platform:

   SUSE LINUX 10.1:
             255c99f43b24995a085ac869082d0f32
             ab68460091ac8995290a3476b5b8dbeb

   SUSE LINUX 10.0:
             dd3d6f3700e9e84294cf157c3a3141c1
             89c7e004bb73629eac71ad642e8826d2

   SUSE LINUX 9.3:
             dc57b898b4f43645c2fe18b58195de90
             cf7b7c04fc9e27684aa97206cd3ae0e0

   SUSE LINUX 9.2:
             e54678b3168c214400c30001c33f3d2d
             200b096a9a37b183c7ef75ae0b5b0b0c

   Power PC Platform:

   SUSE LINUX 10.1:
             f02d12d3ce4e303676efb1cf37d26b11
             b577d22c8914b0cd36eb6187e9de6dfc

   SUSE LINUX 10.0:
             3bd330de35c5e59775883e541af6aa91
             04ea40beed9130fb5f11eda80b248f31

   x86-64 Platform:

   SUSE LINUX 10.1:
             55f9631c5a7a10f3a7d56016cabe3908
             f6c77143b56d82e78701db5b56a481d1

   SUSE LINUX 10.0:
             32a2412b4f35461f530f73c95b5e85c2
             0d89fa02d44e4ca99e237e3812fd4577

   SUSE LINUX 9.3:
             cf96c984dffb0c10ac339d917e8ef97d
             9012087ea4c163b784178a3a7b22d44c

   SUSE LINUX 9.2:
             7e004fedc5ff48a3c13a22d5cc1c2ab4
             78278ce560a5ea87e1a4cf80126712c3

   Sources:

   SUSE LINUX 10.1:
             79f1eb2463e7638789c79ca62d158bea

   SUSE LINUX 10.0:
             023b6d8056ad3dfec1357548d7b8a5ed

   SUSE LINUX 9.3:
             fb5bd0e14208b1434313669fe01e8f07

   SUSE LINUX 9.2:
             c2bc3328b87cc77172b1185d364a8116

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

   UnitedLinux 1.0
   SuSE Linux Openexchange Server 4
   Open Enterprise Server
   Novell Linux POS 9
   Novell Linux Desktop 9
   SuSE Linux Enterprise Server 8
   SuSE Linux Standard Server 8
   SuSE Linux School Server
   SUSE LINUX Retail Solution 8
   SuSE Linux Desktop 1.0
   SUSE SLES 10
   SUSE SLED 10
   SUSE SLES 9
     http://support.novell.com/techcenter/psdb/05412985c36daeff0c33b88942b68c2c.html

______________________________________________________________________________

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