dcsimg
Linux Today: Linux News On Internet Time.




More on LinuxToday


SuSE Linux Advisories: kdenetwork, traceroute-nanog/nkitb

Nov 12, 2002, 17:25 (0 Talkback[s])

____________________________________________________________________________

                        SuSE Security Announcement

        Package:                kdenetwork
        Announcement-ID:        SuSE-SA:2002:042
        Date:                   Tue Nov 12 10:00:00 CET 2002 
        Affected products:      7.2, 7.3
                                SuSE eMail Server III, 3.1
                                SuSE Firewall on CD
                                SuSE Linux Connectivity Server
                                SuSE Linux Enterprise Server 7
                                SuSE Linux Office Server
        Vulnerability Type:     remote command execution
        Severity (1-10):        6
        SuSE default package:   yes
        Cross References:       http://www.kde.org/info/security

    Content of this advisory:
        1) security vulnerability resolved: Remote command execution via
           the lisa lanbrowser.
           problem description, discussion, solution and upgrade information
        2) pending vulnerabilities, solutions, workarounds: problem in
           KDE rlogin:// URL handler
        3) standard appendix (further information)

____________________________________________________________________________

1)  problem description, brief discussion, solution, upgrade information

    During a security review, the SuSE security team has found two
    vulnerabilities in the KDE lanbrowsing service.

    LISa is used to identify CIFS and other servers on the local
    network, and consists of two main modules: "lisa", a network daemon,
    and "reslisa", a restricted version of the lisa daemon.  LISa can
    be accessed in KDE using the URL type "lan://", and resLISa using
    the URL type "rlan://".

    LISA will obtain information on the local network by looking for
    an existing LISA server on other local hosts, and if there is one,
    it retrieves the list of servers from it.  If there is no other LISA
    server, it will scan the network itself.

    SuSE Linux can be configured to run the lisa daemon at system boot
    time. The daemon is not started by default, however.

    The first vulnerability found is a buffer overflow in the lisa
    daemon, and can be exploited by an attacker on the local network
    to obtain root privilege on a machine running the lisa daemon.
    It is not exploitable on a default installation of SuSE Linux,
    because the lisa daemon is not started by default.

    The second vulnerability is a buffer overflow in the lan:// URL
    handler. It can possibly be exploited by remote attackers to gain
    access to the victim user's account, for instance by causing the
    user to follow a bad lan:// link in a HTML document.

    This update provides fixes for SuSE Linux 7.2 and 7.3. Previous
    updates already corrected the vulnerability in SuSE Linux 8.0,
    and SuSE Linux 8.1 contains the fix already.

    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.



    Intel i386 Platform:

    SuSE-7.3:
    ftp://ftp.suse.com/pub/suse/i386/update/7.3/k2de1/kdenetwork-2.2.1-101.i386.rpm
      796ee745cea4f743ba4dc7314d0eab47
    source rpm(s):
    ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/kdenetwork-2.2.1-101.src.rpm
      bdbcc6e939e4fb2f67d92c4998550ebe

    SuSE-7.2:
    ftp://ftp.suse.com/pub/suse/i386/update/7.2/k2de1/kdenetwork-2.1.1-154.i386.rpm
      52168eb8a1f393d5b070e76a40e12040
    source rpm(s):
    ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/kdenetwork-2.1.1-154.src.rpm
      d46367f1c45e557a10854ef9efaa6184



    Sparc Platform:

    SuSE-7.3:
    ftp://ftp.suse.com/pub/suse/sparc/update/7.3/k2de1/kdenetwork-2.2.1-50.sparc.rpm
      0e7fb9026b8fbf8f023bccb6a1ffe9e3
    source rpm(s):
    ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/kdenetwork-2.2.1-50.src.rpm
      c11e3cf176d02bf600d312e527ffa159



    PPC Power PC Platform:

    SuSE-7.3:
    ftp://ftp.suse.com/pub/suse/ppc/update/7.3/k2de1/kdenetwork-2.2.1-88.ppc.rpm
      267805b2368f739ec195bec154b7e04c
    source rpm(s):
    ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/kdenetwork-2.2.1-88.src.rpm
      7f52f011e7b7535b0396fe5d00cf04a8



____________________________________________________________________________

2)  Pending vulnerabilities in SuSE Distributions and Workarounds:

    In KDE 2.x and KDE 3.x, there is a vulnerability in the handler for
    rlogin:// URLs, which allows remote attackers to execute arbitrary
    shell commands with the privileges of the victim user. A similar
    vulnerability exists in KDE 2.x in the handler for telnet:// URLs.

    The SuSE KDE team is in the process of preparing a kdelibs update
    for SuSE Linux. In the interim, we recommend the to disable KDE
    support for rlogin as a workaround. On KDE 3.0, execute the following
    command as root:

         rm /opt/kde3/share/services/rlogin.protocol

    On KDE 2, execute these commands:

        rm /opt/kde2/share/services/rlogin.protocol
        rm /opt/kde2/share/services/telnet.protocol

____________________________________________________________________________

3)  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 <name-of-the-file.rpm>
       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 <file.rpm>
       to verify the signature of the package, where <file.rpm> 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 ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .


  - 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-subscribe@suse.com>.

    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
                <suse-security-announce-subscribe@suse.com>.

    For general information or the frequently asked questions (faq) 
    send mail to:
        <suse-security-info@suse.com> or
        <suse-security-faq@suse.com> respectively.

    =====================================================================
    SuSE's security contact is <security@suse.com> or <security@suse.de>.
    The <security@suse.de> public key is listed below.
    =====================================================================
____________________________________________________________________________

    The information in this advisory may be distributed or reproduced,
    provided that the advisory is not modified in any way. In particular,
    it is desired that the clear-text signature shows proof of the
    authenticity of the text.
    SuSE Linux AG makes no warranties of any kind whatsoever with respect
    to the information contained in this security advisory.

Type Bits/KeyID    Date       User ID
pub  2048R/3D25D3D9 1999-03-06 SuSE Security Team <security@suse.de>
pub  1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>


____________________________________________________________________________

                        SuSE Security Announcement

        Package:                traceroute-nanog/nkitb
        Announcement-ID:        SuSE-SA:2002:043
        Date:                   Tuesday, Nov 12th 2002 09:30 MEST
        Affected products:      7.0, 7.1, 7.2, 7.3, 8.0
                                SuSE eMail Server 3.1
                                SuSE eMail Server III
                                SuSE Firewall Adminhost VPN
                                SuSE Linux Admin-CD for Firewall
                                SuSE Firewall on CD 2 - VPN
                                SuSE Firewall on CD 2
                                SuSE Linux Connectivity Server
                                SuSE Linux Enterprise Server 7
                                SuSE Linux Office Server
        Vulnerability Type:     local root
        Severity (1-10):        4
        SuSE default package:   yes
        Cross References:       none

    Content of this advisory:
        1) security vulnerability resolved: - dropping root after gaining
                                              raw socket
                                            - a few buffer overflows
        2) pending vulnerabilities, solutions, workarounds:
            - ypserv
            - horde
            - openssh
            - wrong MD5 sums in advisory SuSE-SA:2002:041
        3) standard appendix (further information)

____________________________________________________________________________

1)  problem description, brief discussion, solution, upgrade information

    Traceroute is a tool that can be used to track packets in a TCP/IP
    network to determine it's route or to find out about not working
    routers.
    Traceroute-nanog requires root privilege to open a raw socket. It
    does not relinquish these privileges after doing so. This allows
    a malicious user to gain root access by exploiting a buffer
    overflow at a later point.

    For all products prior to 8.1, the traceroute package
    contains the NANOG implementation. This package is installed by
    default. Starting with 8.1, SuSE Linux contains a traceroute program
    rewritten by Olaf Kirch that does not require root privileges anymore.
    This version of traceroute is not vulnerable.

    This is the first update for the traceroute package on the SuSE Linux
    distributions 7.1 through 8.0. We have changed the version string in
    the update packages to read "6.x" instead of the former "nanog_6.x" to
    enable a clean comparison between version numbers. This change is
    misleading in that it suggests that the package name has been changed.
    Since only the version string is affected, the name of the package
    remains the same.

    As a workaround you can remove the setuid bit or just allow trusted
    users to execute traceroute-nanog.
    Become root and add the following line to /etc/permissions.local:
      "/usr/sbin/traceroute          root.trusted    4750"
    This line will keep the setuid root bit for /usr/sbin/traceroute
    and just allow users in group trusted to execute the binary.
    To make the permission change and keep it permanent you have to
    run chkstat(8):
      "chkstat -set /etc/permissions.local"

    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.

    Missing packages are being built and tested and will be available for
    download soon.


    Intel i386 Platform:

    SuSE-8.0:
      ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/traceroute-6.1.1-0.i386.rpm
        afe01bf0b151eca2f42fa5737c99bdc7
    source rpm(s):
      ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/traceroute-6.1.1-0.src.rpm
        ee35e7cf554daa37a3976f473d4192f1

    SuSE-7.3:
      ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/traceroute-6.1.1-0.i386.rpm
        0ef0c0153532fcefdf776311503e590b
    source rpm(s):
      ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/traceroute-6.1.1-0.src.rpm
        15a9f3dba6339f0a0bb57ce17d2d9894

    SuSE-7.2:
      ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/traceroute-6.1.1-0.i386.rpm
        3b9acb72a3208e3e4e92c0df8ab8d46f
    source rpm(s):
      ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/traceroute-6.1.1-0.src.rpm
        a6fd1c7dc3bea4d08ef1efdcbc30fff6

    SuSE-7.1:
      ftp://ftp.suse.com/pub/suse/i386/update/7.1/n1/traceroute-6.0-0.i386.rpm
        1ac8de3a6e54451bae8e3068f2fbd1e9
    source rpm(s):
      ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/traceroute-6.0-0.src.rpm
        291036123b377184fdf0231d6878f57d


    SuSE-7.0:
      ftp://ftp.suse.com/pub/suse/i386/update/7.0/a1/nkitb-2002.11.6-0.i386.rpm
        b1105bc6916a5fdbd54db63d52ec3d81
    source rpm(s):
      ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/nkitb-2002.11.6-0.src.rpm
        3061bd5e551995d62c96da133927a612




    Sparc Platform:

    SuSE-7.3:
      ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/traceroute-6.1.1-0.sparc.rpm
        638b868bedab639292d740e60cd0b266
    source rpm(s):
      ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/traceroute-6.1.1-0.src.rpm
        10a996ae6a2b4b739bca8f5e9d65e2da




    AXP Alpha Platform:

    SuSE-7.1:
      ftp://ftp.suse.com/pub/suse/axp/update/7.1/n1/traceroute-6.0-0.alpha.rpm
        f2d241cd2331bb3de3382b338fba50b8
    source rpm(s):
      ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/traceroute-6.0-0.src.rpm
        949737f63fe99b4476b9c325bdc966fc

    SuSE-7.0:
      ftp://ftp.suse.com/pub/suse/axp/update/7.0/a1/nkitb-2002.11.6-0.alpha.rpm
        04a5746b70af2e99f8a31b86e16cb470
    source rpm(s):
      ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/nkitb-2002.11.6-0.src.rpm
        83abbae6c15ee25adc702047d41a6564




    PPC Power PC Platform:

    SuSE-7.3:
      ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/traceroute-6.1.1-0.ppc.rpm
        a00ed346efdc8992b6cf92b890dcc7db
    source rpm(s):
      ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/traceroute-6.1.1-0.src.rpm
        8bfd655104212afc745ea998f0fe6d84

    SuSE-7.1:
      ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n1/traceroute-6.0-0.ppc.rpm
        0dc4fa991f1b6a2260af694b9b73ff1a
    source rpm(s):
      ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/traceroute-6.0-0.src.rpm
        9e60c951a66e635cab2aa46559f4aa4e

    SuSE-7.0:
      ftp://ftp.suse.com/pub/suse/ppc/update/7.0/a1/nkitb-2002.11.6-0.ppc.rpm
        eb7d62c5e6ae971a6a96d8a475b8d9fb
    source rpm(s):
      ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/nkitb-2002.11.6-0.src.rpm
        c4b5a31e58a91b5dbd0b6ba497e69046


____________________________________________________________________________

2)  Pending vulnerabilities in SuSE Distributions and Workarounds:

  - horde
  There was a cross-site scripting vulnerability in horde.
  Updated packages have been released for 7.3, 8.0 and 8.1.

  - openssh
  When the SSH daemon finds that a user's password has expired,
  the user is forced to set a new password. While doing so, sshd
  did not turn off the terminal echo, causing the password to
  be visible on the screen as it was typed. We are in the process
  of releasing updated package for 7.0 through 7.3. SuSE Linux 8.0
  and 8.1 are not affected.

  - ypserv
  Thorsten Kukuk found a memory leak in ypserv that caused it to lose
  small amounts of memory each time it processes certain malformed
  requests. This could be used by an attacker to kill ypserv by repeating
  this exercise until it runs out of memory.
  We have released updated packages for 7.0 through 8.0. SuSE Linux 8.1
  is not affected.

  - wrong MD5 sums in advisory SuSE-SA:2002:041
  Due to a mistake the SuSE Security Announcement SuSE-SA:2002:041
  (perl-Mailtools) contains wrong MD5 sums.
  A new version will be published on our security web sites soon.

____________________________________________________________________________

3)  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 <name-of-the-file.rpm>
       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 <file.rpm>
       to verify the signature of the package, where <file.rpm> 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 ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .


  - 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-subscribe@suse.com>.

    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
                <suse-security-announce-subscribe@suse.com>.

    For general information or the frequently asked questions (faq)
    send mail to:
        <suse-security-info@suse.com> or
        <suse-security-faq@suse.com> respectively.

    =====================================================================
    SuSE's security contact is <security@suse.com> or <security@suse.de>.
    The <security@suse.de> public key is listed below.
    =====================================================================
____________________________________________________________________________

    The information in this advisory may be distributed or reproduced,
    provided that the advisory is not modified in any way. In particular,
    it is desired that the clear-text signature shows proof of the
    authenticity of the text.
    SuSE Linux AG makes no warranties of any kind whatsoever with respect
    to the information contained in this security advisory.

Type Bits/KeyID    Date       User ID
pub  2048R/3D25D3D9 1999-03-06 SuSE Security Team <security@suse.de>
pub  1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>



Bye,
     Thomas
-- 
  Thomas Biege <thomas@suse.de>
  SuSE Linux AG,Deutschherrnstr. 15-19,90429 Nuernberg
  Function: Security Support & Auditing
  "lynx -source http://www.suse.de/~thomas/contact/thomas.asc | pgp -fka"
  Key fingerprint = 51 AD B9 C7 34 FC F2 54  01 4A 1C D4 66 64 09 83
-- 

  Cold silence has a tendency to atrophy any sense of compassion
                                                  - Maynard James Keenan