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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                krb5
        Announcement ID:        SUSE-SA:2007:025
        Date:                   Thu, 05 Apr 2007 08:00:00 +0000
        Affected Products:      SUSE LINUX 9.3
                                SUSE LINUX 10.0
                                SUSE LINUX 10.1
                                openSUSE 10.2
                                SUSE SLED 10
                                SUSE SLES 10
        Vulnerability Type:     remote code execution
        Severity (1-10):        7
        SUSE Default Package:   no
        Cross-References:       CVE-2007-0956, CVE-2007-0957, CVE-2007-1216

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             krb5 remote root access
           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

   The krb5 telnet daemon allowed remote attackers to skip
   authentication and gain root access (CVE-2007-0956)
   
   A bug in the function krb5_klog_syslog() leads to a buffer overflow
   which could be exploited to execute arbitrary code (CVE-2007-0957).
   
   A double-free bug in the GSS-API library could crash kadmind. It's
   potentially also exploitable to execute arbitrary code
   (CVE-2007-1216).

2) Solution or Work-Around

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

3) Special Instructions and Notes

   Please restart all running instances of ktelnet, kadmind and krb5kdc 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.

   
   x86 Platform:
   
   openSUSE 10.2:
             26a0bdf08d2dbd101c709d87a5db699f
             0edcac30ee95ec906edda22f365c4e64
             c44d965aa89a21dc94dfdd56c1384da9
             999c1c656b63e87ea1ac1623b9c50164
   
   SUSE LINUX 10.1:
             7b881bf501106728a342efa05b6a4534
             89328e997226eb694a5e0ecd6b7184cb
             6d2d02f303a14ade9ea0cf58973b7c8f
             077c19dcbe2cd47f4e33965b26f28081
   
   SUSE LINUX 10.0:
             9d0faa22f0be37e6554e474c4962745e
             fc0e696b9b15d45f01064805df0ca834
             12947fc197652934ab409cc389f08fce
             83b706f6b5a4a5c858091b986c02fe75
   
   SUSE LINUX 9.3:
             616bfe9bc39ac812cb6b2a942d27e7a2
             70cadd7c22ff178fab3d6b8bb8f7be88
             1ca76aed1daf3094596015f26749f8f8
             f475df44f758bf2910304ed9b4eec231
   
   Power PC Platform:
   
   openSUSE 10.2:
             b68d2db6218b681c77a4241a39f7c67a
             2a9ed5a41caeb641975e6307158063a2
             5b8d693d1544bd40e8082c6e12ec0acf
             7bbc1437ca516c641fad79c49549f244
   
   SUSE LINUX 10.1:
             70ad6ad3e77010409663c9137ccdff2b
             e66dd547a934498e6108d64199e6c353
             08e6e8346ffe096c3309a99ccd0b12b2
             57529c2d8435dee24104c521b2ad7da7
   
   SUSE LINUX 10.0:
             bc5f97b09e202dcb98d6fadb9d041248
             a6a1ba40f9156dd2819c39fb90ef749d
             0af5b5bdf4c4c2bdd18ed2f421d53a75
             d9f496d174e43469fac4cfeded0c0a82
   
   x86-64 Platform:
   
   openSUSE 10.2:
             e60d6997238b987a5e0ad0d84433e6f1
             28caf0827d9387f68df2cb9cb4783355
             b8f9eec03f72ffe3a46afb3579bfae67
             dbe5651582cb39caf00e7ea2052e6d12
             4ac292f8860332bf65bc4005342aa35c
             f79187862cf981cee47a3313a463c129
   
   SUSE LINUX 10.1:
             01757ce948cb4a898933156893f14dd6
             a2d72aaa77511f5cad87158c1886dbfc
             7588028cd5441a560482ad90576e9ab0
             67de19bc407e36eed765b599df742f48
             ba747d62adbd54dd1b42bf14ead9c889
             42fc6e61b34ddecd751ab51246d3c27d
   
   SUSE LINUX 10.0:
             af41e738c412e6841005384f33d58906
             d27b0632e5b00dfba8f7aff8c4738a8f
             b2435d5fc3233a51afbd3679386d390e
             561635be7ef4d7abe779e583199c3e1b
             ab63ff82da54a8fde67e31e1a48868a3
             dfa24c69d9bd6dfa1567bb8561ad3ef6
   
   SUSE LINUX 9.3:
             3ea6314d225d3198431743ea0092fdad
             40d307359582effc227a03d06ff66f31
             444d50dd8701a96886b54ff6f4dc26b9
             0c3d27f6df28338fdc6d7f6b4b704792
             388495c9ac888d1958494cf8eda940a5
             4d20b1ccd8b14aa275e67c8825fa8dd6
   
   Sources:
   
   openSUSE 10.2:
             6913ddbdda37edbecfa45bad5e102a36
   
   SUSE LINUX 10.1:
             1aeef8c2789f8af41ac3bd312b57495f
   
   SUSE LINUX 10.0:
             f964e35737b866039464aa92bad5a3f3
   
   SUSE LINUX 9.3:
             0f1675dcc96688e87765dc74aa40bcac
   
   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:
   
   SUSE SLED 10
     http://support.novell.com/techcenter/psdb/42f0e56eca083c9a097518ef837c4be9.html
   
   SUSE SLES 10
     http://support.novell.com/techcenter/psdb/42f0e56eca083c9a097518ef837c4be9.html
     http://support.novell.com/techcenter/psdb/52baa515f293dac164a0c0da920b5531.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:

    opensuse-security@opensuse.org
        -   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
                .

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