______________________________________________________________________________

                        SuSE Security Announcement

        Package:                lprold
        Announcement-ID:        SuSE-SA:2001:033
        Date:                   Wed Oct 10 11:03:12 GMT 2001
        Affected SuSE versions: [6.1, 6.2,] 6.3, 6.4, 7.0, 7.1, 7.2
        Vulnerability Type:     bufferoverflow/local privilege escalation
        Severity (1-10):        6
        SuSE default package:   yes
        Other affected systems: Other Linux distributions, *BSD

    Content of this advisory:
        1) security vulnerability resolved: Several problems in lprold
           problem description, discussion, solution and upgrade information
        2) pending vulnerabilities, solutions, workarounds
        3) standard appendix (further information)

______________________________________________________________________________

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


    ISS X-Force reported an overflow in BSD's lineprinter daemon shipped with
    the lprold package in SuSE Linux. Due to missing bounds checks in the
    lockfile processing function, internal buffers may overflow. Bounds checks
    have been added to fix that problem.
    Additionally the SuSE Security Team uncovered other security releated bugs
    in lpd while analyzing lpd source after receiving the X-Force advisory.
    These bugs allows users on machines listed in /etc/hosts.lpd or
    /etc/hosts.equiv to chown any file on the system running lpd to any user.
    In order to trigger any of the fixed bugs (including the overflow) the
    attackers machine must be listed in one of these two access-files and the
    attacker usually needs root on these machines due to the privileged-port
    requirement.
    Please download the packages and verify them as described in section 3.
    After successful authentication you can update your packages with
    the command `rpm -Uhv file.rpm'.
    As root invoke the command "/etc/rc.d/lpd stop" to shutdown the old lpd
    daemon and "/etc/rc.d/lpd start" afterwards to start the patched daemon.


    i386 Intel Platform:

    SuSE-7.2
      
      23b8251411a557563cb314102f405d31
    source rpm:
      
      ff590e05f2a7c85e9d234bd32d12b13a

    SuSE-7.1
      
      b6efc424262ec9aaa39ac84f230b3df2
    source rpm:
      
      5a95de121c7520bf33620dddbfdda611

    SuSE-7.0
      
      10792a921880048970f40470f1b94330
    source rpm:
      
      094b06515dfd865c6dffedf70de5e6cc

    SuSE-6.4
      
      da1b920d23694a807f91c74301b47ced
    source rpm:
      
      c2c45f04a2d44e374689346f488e8c52

    SuSE-6.3
      
      8f7c5538e878f197de1e6dacdb6a8479
    source rpm:
      
      d13f74f6449ee40b98b2ed0e42e9d2ec



    Sparc Platform:

    SuSE-7.1
      
      78a947db44bc4a41cb33eee1b931b99e
    source rpm:
      
      2c873632eaa6f01efb45cba3f1308cd3

    SuSE-7.0
      
      45320846ee6143fdfc27a7d578f630bd
    source rpm:
      
      1be6f31b6924f81fb965b0dce053f6cb



    AXP Alpha Platform:

    SuSE-7.1
      
      94af7565e8920cdce6e1e7c51f562fba
    source rpm:
      
      0757d322145ef6c2179c8e31b1169cd2

    SuSE-7.0
      
      3c6a2b2b21fcc1b94974aca6c5930e98
    source rpm:
      
      0222dec4d0287b9f1f267b86e8e8a4dd

    SuSE-6.4
      
      f4c618b43a95bd94ed679c1c2119a7aa
    source rpm:
      
      0430ec91e7515d79326ed16f492ea60e

    SuSE-6.3
      
      68a8b9a26e17ed5183b8385be349c6a9
    source rpm:
      
      582d925d8328f79bc566dddcc62f763b



    Power PC Platform:

    SuSE-7.1
      
      3c16c1975b8f9dae3ccfb67dd5f462db
    source rpm:
      
      37b0d3534e39273e158eba42f75f8e31

    SuSE-7.0
      
      d0e5a115d8991e711ef75fc8b06e1d97
    source rpm:
      
      e4d589e9225365b103b502a26d0fd73f

    SuSE-6.4
      
      f8e7557f995388564f98e9bae4708e4e
    source rpm:
      
      78a647beeaf5a5541cb15aa6435ba65e



______________________________________________________________________________

2)  Pending vulnerabilities in SuSE Distributions and Workarounds:

  - sftp/openssh:
    Our last announcement SuSE-SA:2001:032 about WindowMaker claimed
    that the openssh packages on SuSE distributions do not contain the
    sftp-server as described by Peter W <peterw@usa.net> on the bugtraq
    mailing list. This is wrong: The program is indeed included on all
    recent openssh packages of SuSE Linux distributions, starting with
    SuSE Linux 6.4 where the openssh package appeared first.
    We will provide fixes for the distributions 6.4 through 7.2 as soon as
    possible on our ftp server (ftp.suse.de for 6.4-7.0, ftp.suse.com for
    7.1 and newer) and announce these fixes in the section 2) of an
    upcoming security announcement.
    Please note that this error has been corrected shortly before the
    release of the upcoming SuSE Linux 7.3 which will arrive in the stores
    by the end of this week.
    We apologize for this error (Roman Drahtmueller, SuSE Security).

  - squid
    Malformed requests on the client side can cause the squid proxy server
    to die, resulting in a denial of service attack that can be launched
    from the internal network if squid is used at the edge of an internal
    network to proxy requests to the internet.
    We are in the process of testing the update packages that are
    available on the ftp server shortly. SuSE Security will issue a
    dedicated announcement for this issue shortly.

  - devfs/kernel
    SuSE Linux ships the userspace utilities for the use of the devfs
    filesystem in the linux kernel, but neither the utilities nor the
    filesystem interface for device files itself have been used in SuSE
    Linux up to date. The decision to not actively use devfsd in the
    distribution framework is based on security considerations.
    For these reasons, SuSE products are not susceptible to the lately
    found security problems in the devfs implementation.

______________________________________________________________________________

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 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 
       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 uninstalled 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 toplevel directory of the first CD (pubring.gpg)
           and at   .


  - 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 annoucements 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>.
    The <security@suse.com> 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 cleartext signature shows proof of the
    authenticity of the text.
    SuSE GmbH makes no warranties of any kind whatsoever with respect
    to the information contained in this security advisory.