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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                heimdal
        Announcement ID:        SUSE-SA:2006:010
        Date:                   Fri, 24 Feb 2006 12:00:00 +0000
        Affected Products:      SUSE LINUX 9.2
                                SUSE LINUX 9.1
                                SuSE Linux Desktop 1.0
                                SuSE Linux Enterprise Server 8
                                SUSE SLES 9
                                UnitedLinux 1.0
        Vulnerability Type:     remote denial of service
        Severity (1-10):        5
        SUSE Default Package:   no
        Cross-References:       CVE-2006-0582
                                CVE-2006-0677

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

______________________________________________________________________________

1) Problem Description and Brief Discussion

   Heimdal is a Kerberos 5 implementation from the Royal Institut of Techno-
   logy in Stockholm.
   This update fixes two bugs in heimdal. The first one occurs in the rsh
   daemon and allows an authenticated malicious user to gain ownership of
   files that belong to other users (CVE-2006-0582).
   The second bug affects the telnet server and can be used to crash the server
   before authentication happens. It is even a denial-of-service attack when
   the telnetd is started via inetd because inetd stops forking the daemon
   when it forks too fast (CVE-2006-0677).

2) Solution or Work-Around

   There is no work-around known.

3) Special Instructions and Notes

   Please make sure the affected daemons are restarted 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:
   
   SUSE LINUX 9.2:
             3d3d6618cfb387ed34c324d805de0df0
             7f885d8e091ce98a3bab1816d4165d3e
             021f253a7df8d5ab3caa20b25ea67529
             748a213e99d7a2be08eeb4496aecb478
             02b9f64f5be3822307102fb9d5842119
   
   SUSE LINUX 9.1:
             235b22414f6129d744f2f62ffccc7962
             5c17e233db8c0b53798cab0d78f1ede1
             17d0afc2004af42ebbeb8d77af724fe5
             38c61584528fa24ff04ece6705d21fb3
   
   x86-64 Platform:
   
   SUSE LINUX 9.2:
             1f899680ff31945963b55e49df6bcfda
             1d65e94810c65ccff51b75066569c428
             068244c514f752985be7c76c5a25418e
             20b9598b6f5cfaf70de0d3a120f89182
             93dc79bdf0fc7b7b4cd82a0c3769329e
             31d1a3e3da2a794850b3e03710d5263c
             71b87841750ba89979c51c3148d315a0
   
   SUSE LINUX 9.1:
             226be123cb085fb50899ac8af82f5bda
             658aa7a1969078842a0a9368402b83ff
             dafdcf2c26be6576916f5ba6cf3cd9f6
   
   Sources:
   
   SUSE LINUX 9.2:
             e7333885b6976b490164d28dbc00e905
   
   SUSE LINUX 9.1:
             ab5d0a61dbfb9df34dfa200bda28d04a
             0d7fc839fc86c6919931190dbdfbd88e
   
   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:
   
      https://www.suse.com:443/
      https://www.suse.com:443/

______________________________________________________________________________

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

   Please read the weekly 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.
    ====================================================================

SuSE: 2006-010: heimdal Security Update

February 24, 2006
Heimdal is a Kerberos 5 implementation from the Royal Institut of Techno- Heimdal is a Kerberos 5 implementation from the Royal Institut of Techno- logy in Stockholm

Summary


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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                heimdal
        Announcement ID:        SUSE-SA:2006:010
        Date:                   Fri, 24 Feb 2006 12:00:00 +0000
        Affected Products:      SUSE LINUX 9.2
                                SUSE LINUX 9.1
                                SuSE Linux Desktop 1.0
                                SuSE Linux Enterprise Server 8
                                SUSE SLES 9
                                UnitedLinux 1.0
        Vulnerability Type:     remote denial of service
        Severity (1-10):        5
        SUSE Default Package:   no
        Cross-References:       CVE-2006-0582
                                CVE-2006-0677

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

______________________________________________________________________________

1) Problem Description and Brief Discussion

   Heimdal is a Kerberos 5 implementation from the Royal Institut of Techno-
   logy in Stockholm.
   This update fixes two bugs in heimdal. The first one occurs in the rsh
   daemon and allows an authenticated malicious user to gain ownership of
   files that belong to other users (CVE-2006-0582).
   The second bug affects the telnet server and can be used to crash the server
   before authentication happens. It is even a denial-of-service attack when
   the telnetd is started via inetd because inetd stops forking the daemon
   when it forks too fast (CVE-2006-0677).

2) Solution or Work-Around

   There is no work-around known.

3) Special Instructions and Notes

   Please make sure the affected daemons are restarted 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:
   
   SUSE LINUX 9.2:
             3d3d6618cfb387ed34c324d805de0df0
             7f885d8e091ce98a3bab1816d4165d3e
             021f253a7df8d5ab3caa20b25ea67529
             748a213e99d7a2be08eeb4496aecb478
             02b9f64f5be3822307102fb9d5842119
   
   SUSE LINUX 9.1:
             235b22414f6129d744f2f62ffccc7962
             5c17e233db8c0b53798cab0d78f1ede1
             17d0afc2004af42ebbeb8d77af724fe5
             38c61584528fa24ff04ece6705d21fb3
   
   x86-64 Platform:
   
   SUSE LINUX 9.2:
             1f899680ff31945963b55e49df6bcfda
             1d65e94810c65ccff51b75066569c428
             068244c514f752985be7c76c5a25418e
             20b9598b6f5cfaf70de0d3a120f89182
             93dc79bdf0fc7b7b4cd82a0c3769329e
             31d1a3e3da2a794850b3e03710d5263c
             71b87841750ba89979c51c3148d315a0
   
   SUSE LINUX 9.1:
             226be123cb085fb50899ac8af82f5bda
             658aa7a1969078842a0a9368402b83ff
             dafdcf2c26be6576916f5ba6cf3cd9f6
   
   Sources:
   
   SUSE LINUX 9.2:
             e7333885b6976b490164d28dbc00e905
   
   SUSE LINUX 9.1:
             ab5d0a61dbfb9df34dfa200bda28d04a
             0d7fc839fc86c6919931190dbdfbd88e
   
   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:
   
      https://www.suse.com:443/
      https://www.suse.com:443/

______________________________________________________________________________

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

   Please read the weekly 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.
    ====================================================================

References

Severity

Related News