SuSe: lsh buffer overflow vulnerabilities

    Date01 Oct 2003
    CategorySuSE
    2045
    Posted ByLinuxSecurity Advisories
    There are buffer overflow vulnerabilities that allow attackers to execute arbitrary code as root on un-patched systems.
    
    ______________________________________________________________________________
    
                            SuSE Security Announcement
    
            Package:                lsh
            Announcement-ID:        SuSE-SA:2003:041
            Date:                   Wed Oct  1 10:24:45 CEST 2003
            Affected products:      8.0, 8.1, 8.2
            Vulnerability Type:     remote code execution
            Severity (1-10):        5
            SuSE default package:   yes
            Cross References:       -
    
        Content of this advisory:
            1) security vulnerability resolved: Buffer overflow in lsh.
               problem description, discussion, solution and upgrade information
            2) pending vulnerabilities, solutions, workarounds:
                - node
                - proftp
                - OpenSSL
            3) standard appendix (further information)
    
    ______________________________________________________________________________
    
    1)  problem description, brief discussion, solution, upgrade information
    
        LSH is the GNU implementation of SSH and can be seen as an alternative
        to OpenSSH.
          Recently various remotely exploitable buffer overflows have been
        reported in LSH. These allow attackers to execute arbitrary code as root
        on un-patched systems.
          LSH is not installed by default on SuSE Linux. An update is therefore
        only recommended if you run LSH.
        Maintained SuSE products are not affected by this bug as LSH is not
        packaged on maintained products such as the Enterprise Server.
    
        For the updates to take effect execute the following command as root:
    
          /usr/sbin/rclshd restart
    
        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.
    
        i386 Intel Platform:
        SuSE-8.2:
         ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/lsh-1.5-114.i586.rpm
          798f52402cda6c7e1733aed15bf0d9cb
        patch rpm(s):
         ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/lsh-1.5-114.i586.patch.rpm
          9308cdb133d2311a9dc4a10bbf613501
        source rpm(s):
         ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/lsh-1.5-114.src.rpm
          1e1b5beac002cf51d1eea0277934a69d
    
        SuSE-8.1:
         ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/lsh-1.4.2-73.i586.rpm
          b5ff8ba104623fe9a77705154aad92f7
        patch rpm(s):
         ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/lsh-1.4.2-73.i586.patch.rpm
          6341acd3fe513921b7123d7c1d98cc43
        source rpm(s):
         ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/lsh-1.4.2-73.src.rpm
          0a2b95e911f8760009ad0d5b2fd7618e
    
        SuSE-8.0:
         ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec3/lsh-1.3.5-188.i386.rpm
          bccfd85985bab8a324b25c1b2443bf2b
        patch rpm(s):
         ftp://ftp.suse.com/pub/suse/i386/update/8.0/sec3/lsh-1.3.5-188.i386.patch.rpm
          8a232720cb0a4b35d0899e9c6a4e80ae
        source rpm(s):
         ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/lsh-1.3.5-188.src.rpm
          8e3e30b134b12400559152bb5c53d0f8
    
    ______________________________________________________________________________
    
    2)  Pending vulnerabilities in SuSE Distributions and Workarounds:
    
        - node
        A format string vulnerability has been fixed in the new node packages
        available on our ftp servers. An update is recommended if you use this
        package.
    
        - proftp
        A off-by-one buffer overflow has been fixed in the proftp packages for
        SuSE Linux 7.2 and 7.3. Note that the bug that was fixed is different from
        the 'ASCII File Transfer Buffer Overrun Vulnerability' (CAN-2003-0831).
        The proftp packages shipped by SuSE are not affected by CAN-2003-0831.
    
        - OpenSSL
        Critical bugs within the ASN.1 parsing routines have been reported recently.
        We are currently building new packages and will notify you in a separate
        advisory when the packages are available.
    
    ______________________________________________________________________________
    
    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 
           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 This email address is being protected from spambots. You need JavaScript enabled to view it.),
           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 
           to verify the signature of the package, where  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 "This email address is being protected from spambots. You need JavaScript enabled to view it." 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:
    
        This email address is being protected from spambots. You need JavaScript enabled to view it.
            -   general/linux/SuSE security discussion.
                All SuSE security announcements are sent to this list.
                To subscribe, send an email to
                    <This email address is being protected from spambots. You need JavaScript enabled to view it.>.
    
        This email address is being protected from spambots. You need JavaScript enabled to view it.
            -   SuSE's announce-only mailing list.
                Only SuSE's security announcements are sent to this list.
                To subscribe, send an email to
                    <This email address is being protected from spambots. You need JavaScript enabled to view it.>.
    
        For general information or the frequently asked questions (faq)
        send mail to:
            <This email address is being protected from spambots. You need JavaScript enabled to view it.> or
            <This email address is being protected from spambots. You need JavaScript enabled to view it.> respectively.
    
        =====================================================================
        SuSE's security contact is <This email address is being protected from spambots. You need JavaScript enabled to view it.> or <This email address is being protected from spambots. You need JavaScript enabled to view it.>.
        The <This email address is being protected from spambots. You need JavaScript enabled to view it.> 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 <This email address is being protected from spambots. You need JavaScript enabled to view it.>
    pub  1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <This email address is being protected from spambots. You need JavaScript enabled to view it.>
    
    
    You are not authorised to post comments.

    Comments powered by CComment

    LinuxSecurity Poll

    What do you think of the articles on LinuxSecurity?

    No answer selected. Please try again.
    Please select either existing option or enter your own, however not both.
    Please select minimum 0 answer(s) and maximum 3 answer(s).
    /main-polls/24-what-do-you-think-of-the-quality-of-the-articles-on-linuxsecurity?task=poll.vote&format=json
    24
    radio
    [{"id":"87","title":"Excellent, don't change a thing!","votes":"25","type":"x","order":"1","pct":55.56,"resources":[]},{"id":"88","title":"Should be more technical","votes":"5","type":"x","order":"2","pct":11.11,"resources":[]},{"id":"89","title":"Should include more HOWTOs","votes":"15","type":"x","order":"3","pct":33.33,"resources":[]}]["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"]["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"]350
    bottom200

    We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.