dcsimg
Linux Today: Linux News On Internet Time.




More on LinuxToday


SuSE Security Announcement: sdb

Aug 20, 2001, 20:22 (0 Talkback[s])
Date: Mon, 20 Aug 2001 15:44:03 +0200 (CEST)
From: Thomas Biege 
Subject: SuSE Security Announcement: sdb (SuSE-SA:2001:027)

____________________________________________________________________________

                        SuSE Security Announcement

        Package:                sdb
        Announcement-ID:        SuSE-SA:2001:027
        Date:                   Monday, August 20th 2001 10:00 MEST
        Affected SuSE versions: [6.0, 6.1, 6.2,] 6.3, 6.4, 7.0, 7.1, 7.2
        Vulnerability Type:     local (maybe remote) privilege escalation
        Severity (1-10):        4
        SuSE default package:   yes
        Other affected systems: no

        Content of this advisory:
        1) security vulnerability resolved: sdbsearch.cgi
           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

  Sdbsearch.cgi is Perl script which is part of the sdb package of SuSE Linux
  was found vulnerable by using untrustworthy client input (HTTP_REFERER).
  By exploiting this trust an attacker could force the sdbsearch.cgi script
  to open a malicious keylist file which includes keywords and filenames.
  By replacing the filename in the keylist file with the Perl pipe followed
  by arbitrary shell commands the sdbsearch.cgi would execute these commands
  when trying to open these 'filenames'.
  Note, that the attacker needs local access to the machine to store the
  keylist file on the server running sdbsearch.cgi. Misconfigured ftp
  accounts, trojan tar balls or RPM files could also be used.

  Sdbsearch.cgi on SuSE Linux 7.1 and 7.2 is not exploitable, because
  Perl's taint mode is used, nevertheless the HTTP_REFERER variable is still
  unfiltered and fully trusted. So, users of SuSE Linux 7.1 and 7.2 are
  not in danger but should update to avoid future attacks.

  Please update your machines with the new RPMs from our ftp server.


  i386 Intel Platform:

  SuSE-7.2
    ftp://ftp.suse.com/pub/suse/i386/update/7.2/doc1/sdb-2001.5.15-6.noarch.rpm
      4230c06f2e703753e79ee0e50339567b
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/sdb-2001.5.15-6.src.rpm
      7090b18b0f5eeb3a4459134eda2b05ee

  SuSE-7.1
    ftp://ftp.suse.com/pub/suse/i386/update/7.1/doc1/sdb-2001.1.18-2.noarch.rpm
      5db3cb4341829769eea4d1f9c7466800
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/sdb-2001.1.18-2.src.rpm
      97898cb2e0cd184b01dd8e6309ab166b

  SuSE-7.0
    ftp://ftp.suse.com/pub/suse/i386/update/7.0/doc1/sdb-2000.7.14-3.noarch.rpm
      f12bc106ec92359c7c382ef1e103656f
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/sdb-2000.7.14-3.src.rpm
      4c9034a7376f8cf2e554f7d41e57b984

  SuSE-6.4
    ftp://ftp.suse.com/pub/suse/i386/update/6.4/doc1/sdb-2000.3.13-1.noarch.rpm
      0627c5db673924c7f7a5526b3fc56f0d
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/sdb-2000.3.13-1.src.rpm
      d71b0df1e08745f15b8d95d66718e2b4

  SuSE-6.3
    ftp://ftp.suse.com/pub/suse/i386/update/6.3/doc1/sdb-99.11.8-10.noarch.rpm
      9917fe4a3735dfb568a60af8c919c26f
    source rpm:
    ftp://ftp.suse.com/pub/suse/i386/update/6.3/zq1/sdb-99.11.8-10.src.rpm
      3c0d5d7fe8b5720350b501deca82beca



  Sparc Platform:

  SuSE-7.1
    ftp://ftp.suse.com/pub/suse/sparc/update/7.1/doc1/sdb-2001.1.18-0.noarch.rpm
      f33dd4b47cdb20eaec420353a570da41
    source rpm:
    ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/sdb-2001.1.18-0.src.rpm
      a2b3a11161c24decfa7e52ccf668d613

  SuSE-7.0
    ftp://ftp.suse.com/pub/suse/sparc/update/7.0/doc1/sdb-2000.7.14-0.noarch.rpm
      ee8010587e5a6424fd4c83d2dbf0d3ef
    source rpm:
    ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/sdb-2000.7.14-0.src.rpm
      0a2af53aa95673e3f3ee45195f09b4dc



  AXP Alpha Platform:

  SuSE-7.1
    ftp://ftp.suse.com/pub/suse/axp/update/7.1/doc1/sdb-2001.1.18-0.noarch.rpm
      b9329d16642aaa28b3560db19c40ca29
    source rpm:
    ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/sdb-2001.1.18-0.src.rpm
      27df8d88110edb5f9c2476e0f5da2eb0

  SuSE-7.0
    ftp://ftp.suse.com/pub/suse/axp/update/7.0/doc1/sdb-2000.7.14-0.noarch.rpm
      0cbca12b0256424db89d8c0d6d860c7a
    source rpm:
    ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/sdb-2000.7.14-0.src.rpm
      9ff9e6d196f90309c752e0a9308ded56

  SuSE-6.4
    ftp://ftp.suse.com/pub/suse/axp/update/6.4/doc1/sdb-2000.3.13-0.noarch.rpm
      1dc3c27aabadcf64556412e7e388b2d7
    source rpm:
    ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/sdb-2000.3.13-0.src.rpm
      300beb396532ea3ad9b390de90be1cd6

  SuSE-6.3
    ftp://ftp.suse.com/pub/suse/axp/update/6.3/doc1/sdb-99.11.8-2.noarch.rpm
      ab236bf7c71b3081eac9f1897fe3d135
    source rpm:
    ftp://ftp.suse.com/pub/suse/axp/update/6.3/zq1/sdb-99.11.8-2.src.rpm
      07ddf02d2c245bfc6f66e81a25ee99a4



  PPC PowerPC Platform:

  SuSE-7.1
    ftp://ftp.suse.com/pub/suse/ppc/update/7.1/doc1/sdb-2001.1.18-0.noarch.rpm
      aa2e8090238df36f982d9829257bdb7c
    source rpm:
    ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/sdb-2001.1.18-0.src.rpm
      54baed3e4631595f61111b71b7245785

  SuSE-7.0
    ftp://ftp.suse.com/pub/suse/ppc/update/7.0/doc1/sdb-2000.7.14-0.noarch.rpm
      75d51a9cc5ee4ea0dd0a20bceba17383
    source rpm:
    ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/sdb-2000.7.14-0.src.rpm
      2bded9520b27c41a9df74b3a41d73daf

  SuSE-6.4
    ftp://ftp.suse.com/pub/suse/ppc/update/6.4/doc1/sdb-2000.3.13-0.noarch.rpm
      009dcfd705d5528f21b81c2befaa8187
    source rpm:
    ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/sdb-2000.3.13-0.src.rpm
      029868fdc7d369515f0fb8d5b6be2532



____________________________________________________________________________

2)  Pending vulnerabilities in SuSE Distributions and Workarounds:

  Please watch out for more announcements that are currently in our queue.


____________________________________________________________________________

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 advise against subscribing to 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 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 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.

Bye,
     Thomas
-- 
  Thomas Biege, SuSE GmbH, Schanzaeckerstr. 10, 90443 Nuernberg
  E@mail: thomas@suse.de      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 84