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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                kdelibs3
        Announcement-ID:        SUSE-SA:2005:022
        Date:                   Mon, 11 Apr 2005 15:00:00 +0000
        Affected products:      9.1, 9.2, 9.3
                                SUSE Linux Enterprise Server 9
                                Novell Linux Desktop 9
        Vulnerability Type:     remote code execution
                                local denial of service
        Severity (1-10):        8
        SUSE default package:   yes
        Cross References:       CAN-2005-0237
                                CAN-2005-0396

    Content of this advisory:
        1) security vulnerability resolved:
             several security problems in KDE
           problem description
        2) solution/workaround
        3) special instructions and notes
        4) package location and checksums
        5) pending vulnerabilities, solutions, workarounds:
            See SUSE Security Summary Report.

        6) standard appendix (further information)

______________________________________________________________________________

1) problem description, brief discussion

    Several vulnerabilities have been identified and fixed in the KDE
    desktop environment.

    - A buffer overflow via specially crafted PCX pictures was fixed.

      This could lead to a remote attacker being able to execute code
      as the user opening or viewing a PCX images. This PCX image could
      have been embedded within a web page or Email.

      This affects SUSE Linux 9.1 up to 9.3, SUSE Linux Enterprise Server
      9 and Novell Linux Desktop 9.


    - The IDN domain name cloaking problem was fixed.

      A remote website could disguise its name as another potentially
      trusted site by using a extension originally meant for non-ASCII
      domain names by using "homographs" which look exactly like other
      letters.

      The fix used by KDE is only use homographs for trusted domains.
      It is disabled by default for the .net, .com and .org domains.

      This issue exists in SUSE Linux 9.1 and 9.2, SUSE Linux Enterprise
      Server 9 and Novell Linux Desktop 9.  It has been assigned the
      Mitre CVE ID  CAN-2005-0233.


    - A denial of service attack against the DCOP service was fixed.

      A local user could cause another users KDE session to visible hang
      by writing bad data to the world writable DCOP socket. The socket
      has been made writable only for the user itself.

      This was found by Sebastian Krahmer of SUSE Security.

      This affects all SUSE Linux versions, except SUSE Linux 9.3.
      Updates for SUSE Linux up to 9.0 and SUSE Linux Enterprise Server
      8 are not included for this minor issue. They will be included
      should a later security update for different issues be necessary.

      This is tracked by the Mitre CVE ID CAN-2005-0396.

    Additionally following bug was fixed:

    - A possible race in the DNS resolver causing unresolved hosts in rare
      cases was fixed.  This only affected SUSE Linux 9.3.

2) solution/workaround

    Please install the updated packages.

3) special instructions and notes

    Make sure you restart your KDE session after this update.

4) package location and checksums

    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.


    x86 Platform:

    SUSE Linux 9.3:
               6b63160218d7e9023418980186942ab3
               7de0dcf016ad28f3f95c9110a376dc7b

    SUSE Linux 9.2:
               47c8c9ccb24b30261de0910ff5bfa19e
               7da9ca5c0cefb043ea170c59beaa588a

    SUSE Linux 9.1:
               6dd4f0b38a750f256f6639decda2a968
               955791a7b3973698f2c9ea8b0cd09716
    source rpm(s):
               3f5585b97d663b7d6d9bcac0f8c0b7a0

    x86-64 Platform:

    SUSE Linux 9.3:
               5c79a3e9e143bd0c29ecbf7d4b4222a2
    source rpm(s):
               6a3f653fe866b9cfb7f9215fed404e94

    SUSE Linux 9.2:
               d2970930a5757b3a2758eb53efda5d8b
    source rpm(s):
               4ae72b2108db739ebc4aefca67b5b566

    SUSE Linux 9.1:
               7355ab449354f49fdc0de161d6fb86ab
    source rpm(s):
               1587e0cfa6ce3dae17c4f6fa8c10ef01


______________________________________________________________________________

5)  Pending vulnerabilities in SUSE Distributions and Workarounds:

    See SUSE Security Summary Report.

______________________________________________________________________________

6)  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.
    ====================================================================