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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kdelibs/kdelibs3
        Announcement-ID:        SuSE-SA:2003:014
        Date:                   Wed May 26 12:00:00 MEST 2004
        Affected products:      8.0, 8.1, 8.2, 9.0, 9.1
                                SuSE Linux Database Server,
                                SuSE Linux Enterprise Server 7, 8
                                SuSE Linux Firewall on CD 2
                                SuSE Linux Connectivity Server
                                SuSE Linux Office Server
                                SuSE Linux Desktop 1.0
        Vulnerability Type:     remote file creation
        Severity (1-10):        6
        SUSE default package:   yes
        Cross References:       CAN-2004-0411


    Content of this advisory:
        1) security vulnerability resolved: URI file creation vulnerability
           problem description, discussion, solution and upgrade information
        2) pending vulnerabilities, solutions, workarounds:
            - rsync
            - film
            - apache/mod_ssl
        3) standard appendix (further information)

______________________________________________________________________________

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

    The kdelibs3 (kdelibs for SLES7 based products) package is a core package
    for the K desktop environment (KDE). The URI handler of the kdelibs3
    and kdelibs class library contains a flaw which allows remote
    attackers to create arbitrary files as the user utilizing the
    kdelibs3/kdelibs package.
      Affected are applications which use the kdelibs3/kdelibs URI handler
    such as Konqueror or Kmail.
      The original KDE advisory can be found at
    https://kde.org/info/security/advisory-20040517-1.txt
    

    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-9.1:
          3724021df2c50d25729c85ccbc1c6e0b
    patch rpm(s):
          eb07494e104d37c02430c8e8a451c8c0
    source rpm(s):
          bda5d53abd4c21ac641cf551a004f847

    SuSE-9.0:
          15b6948b8331d58e069fef80165e34ec
    patch rpm(s):
          f523a907f1e3d5aaf9e77632be339b78
    source rpm(s):
          5fae5675cf3a8ba15e26a1467818de13

    SuSE-8.2:
          5c0a195dd90018f2f2fdc26c0f3aa414
    patch rpm(s):
          1bd13baccb08418a86d1dd6a076d7a85
    source rpm(s):
          2f281da09839e883fc3e7a173928accb

    SuSE-8.1:
          7f65572c6011fcb9745a93df71661b74
    patch rpm(s):
          2a177303c21e7d109642450fd6b5a456
    source rpm(s):
          b717891fbabdf0fb6f01098f6ec4628c

    SuSE-8.0:
          775562f135feac98e007d5f8e21bbbd7
    patch rpm(s):
          91032e4cb6bc77263fc4156195f63e92


    Opteron x86_64 Platform:

    SuSE-9.1:
          19f3520ee5c742ad7994f3426a0ea7f3
    patch rpm(s):
          c089127df66d98c1a9e1a561fb9c1f0b
    source rpm(s):
          2b25abf3d206152711a0a5597d343f4a

    SuSE-9.0:
          c136da67c2a288177ceb7bfe537ac248
    patch rpm(s):
          b0886ca176fa3f54b42da642a26554d0
    source rpm(s):
          e0d10e3b23142eb6ee95cbb5afad71da


______________________________________________________________________________

2)  Pending vulnerabilities in SUSE Distributions and Workarounds:

    - rsync
    rsync prior to version 2.6.1 does not properly sanitize paths
    when running as read/write daemon without chroot. New update packages
    are available on our ftp servers which fix this problem.

    - film
    The film program creates temporary files in an insecure way. New
    update packages are available on our ftp servers.

    - apache/mod_ssl
    A buffer overflow in a uuencode function of mod_ssl has been fixed as
    well as various minor bugs (CAN-2003-0987, CAN-2003-0020, CAN-2004-0174
    and CAN-2003-0993). New packages are currently being tested and will
    soon be available on our ftp servers.

______________________________________________________________________________

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 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-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
                .

    For general information or the frequently asked questions (faq) 
    send mail to:
         or
         respectively.

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================