From: Sune Kloppenborg Jeppesen <jaervosz@gentoo.org>
To: gentoo-announce@robin.gentoo.org
Cc: bugtraq@securityfocus.com, full-disclosure@lists.grok.org.uk,
security-alerts@linuxsecurity.com
Subject: [gentoo-announce] [ GLSA 200503-22 ] KDE: Local Denial of Service
Date: Sat, 19 Mar 2005 09:28:33 +0100 [thread overview]
Message-ID: <200503190928.37385.jaervosz@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2581 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 200503-22
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Normal
Title: KDE: Local Denial of Service
Date: March 19, 2005
Bugs: #83814
ID: 200503-22
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
KDE is vulnerable to a local Denial of Service attack.
Background
==========
KDE is a feature-rich graphical desktop environment for Linux and
Unix-like Operating Systems. DCOP is KDE's simple IPC/RPC mechanism.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 kde-base/kdelibs < 3.3.2-r7 >= 3.3.2-r7
*>= 3.2.3-r8
Description
===========
Sebastian Krahmer discovered that it is possible to stall the
dcopserver of other users.
Impact
======
An attacker could exploit this to cause a local Denial of Service by
stalling the dcopserver in the authentication process. As a result all
desktop functionality relying on DCOP will cease to function.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All kdelibs users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose kde-base/kdelibs
References
==========
[ 1 ] CAN-2005-0396
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-0396
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
http://security.gentoo.org/glsa/glsa-200503-22.xml
Concerns?
=========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
http://bugs.gentoo.org.
License
=======
Copyright 2005 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
http://creativecommons.org/licenses/by-sa/2.0
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2005-03-19 8:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200503190928.37385.jaervosz@gentoo.org \
--to=jaervosz@gentoo.org \
--cc=bugtraq@securityfocus.com \
--cc=full-disclosure@lists.grok.org.uk \
--cc=gentoo-announce@robin.gentoo.org \
--cc=security-alerts@linuxsecurity.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox