Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Sign up!
EnGarde Community
What is the most important Linux security technology?
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Latest Newsletters
Linux Security Week: March 23rd, 2015
Linux Advisory Watch: March 20th, 2015
LinuxSecurity Newsletters
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

SuSE: various KDE security problems Print E-mail
User Rating:      How can I rate this item?
Posted by Benjamin D. Thomas   
SuSE Several vulnerabilities have been identified and fixed in the KDE desktop environment.

                        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

    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

      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:

    SUSE Linux 9.2:

    SUSE Linux 9.1:
    source rpm(s):

    x86-64 Platform:

    SUSE Linux 9.3:
    source rpm(s):

    SUSE Linux 9.2:
    source rpm(s):

    SUSE Linux 9.1:
    source rpm(s):


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

  - SUSE runs two security mailing lists to which any interested party may
        -   general/linux/SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an email to
        -   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:

    SUSE's security contact is  or .
    The  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.
< Prev   Next >


Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Yesterday's Edition
Tech Companies, Privacy Advocates Call for NSA Reform
Google warns of unauthorized TLS certificates trusted by almost all OSes
How Kevin Mitnick hacked the audience at CeBIT 2015
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2015 Guardian Digital, Inc. All rights reserved.