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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                krb5
        Announcement ID:        SUSE-SA:2008:016
        Date:                   Wed, 19 Mar 2008 10:00:00 +0000
        Affected Products:      SUSE LINUX 10.1
                                openSUSE 10.2
                                openSUSE 10.3
                                SUSE Linux Enterprise Desktop 10 SP1
                                SLE SDK 10 SP1
                                SUSE Linux Enterprise Server 10 SP1
        Vulnerability Type:     remote code execution
        Severity (1-10):        7
        SUSE Default Package:   no
        Cross-References:       CVE-2008-0062
                                CVE-2008-0063
                                CVE-2008-0947
                                CVE-2008-0948

    Content of This Advisory:
        1) Security Vulnerability Resolved:
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   The krb5 package is the implementation of the Kerberos protocol suite
   from MIT.
   This update fixes three vulnerabilities, two of them are only possible if
   krb4 support is enabled:
   - CVE-2008-0062:   null/dangling pointer (krb4) 
   - CVE-2008-0063:   operations on uninitialized buffer content,
                      possible information leak (krb4) 
   - CVE-2008-0947/8: out-of-bound array
                      access in kadmind's RPC lib

2) Solution or Work-Around

   Please install the new packages.

3) Special Instructions and Notes

   Please restart the kerberos services.

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.3:
             53f6c9b454e27c47ec4cb32679757c48
             66ee0e785595b000842c5cd2c9162c55
             f3fba89b56860b8f46691c69bba8b3c7
             193a8298aa8bb866e19e0c48f23e523e
             a9b01b5c846e02c588664cddcae4c5c6
             ff536136c01b5f900aebe6fdc1ec62e6
   
   openSUSE 10.2:
             5764e87b834c6a5b8a467fa6aa8ec40e
             94db70009c4c6e099a9807584c701686
             5881c8be92dc3eb215a1e837b6468922
             c45980b430614c2371dd1ad4f8d21a34
             1c6a45d60e5eabffedc2c1e3e755ac73
             03793b23aced1c01d9e2817648d7c777
   
   SUSE LINUX 10.1:
             51d1c53aaf25a36dd1e2e74662cbabd9
             6b4d89a932988685993dba1e87aea95f
             c7ff44ef5a8453d5223da71d670fdea4
             bc0456ed7708ee3ffdc2501e849e9dbe
             9942cbbfd032ea80d8a20daa34ce5374
             d4596d47caafa6ea4ee4b4f4e218f831
   
   Power PC Platform:
   
   openSUSE 10.3:
             f0d1399edebb3e1d715d84568065130a
             8e444214994c1e7297b5332d96967ec0
             2eecfe960c969bf3a3dcce2fcab010f0
             8052a7d7a942545a46fa5e962c562ab8
             6a118f48123ebfc23715bf797bf8b7d0
             fd8f73d6d8757d9ce3dea43997b56b0c
   
   openSUSE 10.2:
             04289bb24041d226f27eb92025b25463
             731ea1ef473c0d1c8990a8045a9fe587
             f911f86a0d2e8c9da16930525bd8b163
             a4c560015bbaddcbc88603e1e194146e
             64d0f163ebff972f2e70c6cc4d760555
             8b06dc5e5ac5b3fa410559017403378a
   
   SUSE LINUX 10.1:
             ae1652f3ea622c5c91b0fd1d47b066ef
             a389841f387e37732c80d9d5095f9ae6
             cb6b4e402570e45767c5ae7a5c26e34c
             3a2c13bc932e84f7a451f3a2c77c99f0
             b34f9511e269e0dfc2896ac88cf41cce
             0263cbb8f0f41e50dacfed082eca0835
   
   x86-64 Platform:
   
   openSUSE 10.3:
             6df39c9ddfb04cd4889b5f4bb271213a
             77ba221640964cc90ad8e0010ad5c07e
             fccb50e18045baa2c78165f20eb13eec
             3bfd6270a31f2a6a35728bcd274ae327
             53b3634e9e92255b62a932ed6d30742d
             54071b2e12004117b0599f53c4a6027b
             07069062d1e7b140c6774cc2aaa821d5
             b07d395220662db193b6f54753931ccc
   
   openSUSE 10.2:
             3f2d8918cf5da2cab839bf2c72af1495
             4348a17ec69b6c64c69e11f74fa88a08
             433ffcced3ede0163628854ae3296baf
             c24ab880f1314c1d25f3e9561b204c10
             6022c2534c50718a2a4fd18fde346daf
             d82a0204e6e0f5e9d6bcd8f60aa4fbde
             17dc2896ebc7f252e39fc8e23a41abc1
             45596c22ec6d0c1eebf42f683e4e0cd4
   
   SUSE LINUX 10.1:
             684c7d1363494a7854afd3755bdb2a20
             b8552a99f0785f1eee434f6d7293731a
             060fac873ba1bc13e4b5b813ae6a6cd2
             28235a5328a8a982e2a1784793a17863
             056f5e479561d2b831e3dd969261f8de
             d81c85af0ca1812c273bbd1c6ddf3cb1
             d17b2d40649a83e28afd6a7a3dec96d6
             dd8096c153fb51bdd67352cbe8a51953
   
   Sources:
   
   openSUSE 10.3:
             6ead1c530f58e6255b1c9ba1b78eb3ae
   
   openSUSE 10.2:
             add4417c6743a6dd26f35182e85ee956
   
   SUSE LINUX 10.1:
             2185d5b60fe733640f16a3a561ec6888
   
   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:
   
   SUSE Linux Enterprise Server 10 SP1
     http://support.novell.com/techcenter/psdb/a1cba9b24d53ae5d2b80a81acd449edb.html
   
   SLE SDK 10 SP1
     http://support.novell.com/techcenter/psdb/a1cba9b24d53ae5d2b80a81acd449edb.html
   
   SUSE Linux Enterprise Desktop 10 SP1
     http://support.novell.com/techcenter/psdb/a1cba9b24d53ae5d2b80a81acd449edb.html

______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

   Please read our weekly security 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
                .

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