Disclosure date: 14:00 CET March 16, 2005 KDE Security Advisory: Local DCOP denial of service vulnerability Original Release Date: 20050316 URL: http://www.kde.org/info/security/advisory-20050316-1.txt 0. References http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-0396 1. Systems affected: All KDE version prior to KDE 3.4 on systems where multiple users have access. 2. Overview: Sebastian Krahmer of the SUSE LINUX Security Team reported a local denial of service vulnerability in KDE's Desktop Communication Protocol (DCOP) daemon better known as dcopserver. A local user can lock up the dcopserver of arbitrary other users on the same machine by stalling the DCOP authentication process. Although it is not possible to by pass the authentication process this way, it can cause a significant reduction in desktop functionality for the affected users. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CAN-2005-0396 to this issue. 3. Impact: A local user can lock up the dcopserver of arbitrary other users on the same machine. This can cause a significant reduction in desktop functionality for the affected users including, but not limited to, the inability to browse the internet and the inability to start new applications. 4. Solution: Upgrade to KDE 3.4. For older versions of KDE Source code patches have been made available which fix these vulnerabilities. Contact your OS vendor / binary package provider for information about how to obtain updated binary packages. 5. Patch: A patch for KDE 3.1.x is available from ftp://ftp.kde.org/pub/kde/security_patches 377c49d8224612fbf09f70f3c09d52f5 post-3.1.5-kdelibs-dcop.patch A patch for KDE 3.2.x is available from ftp://ftp.kde.org/pub/kde/security_patches 0948701bffb082c65784dc8a2b648ef0 post-3.2.3-kdelibs-dcop.patch A patch for KDE 3.3.x is available from ftp://ftp.kde.org/pub/kde/security_patches 7309e259ae1f29be08bbb70e580da3fb post-3.3.2-kdelibs-dcop.patch 6. Time line and credits: 21/02/2005 KDE Security informed by SUSE LINUX. 21/02/2005 Patches applied to KDE CVS. 02/03/2005 Vendors notified 16/03/2005 KDE Security Advisory released.
Created attachment 52457 [details, diff] post-3.3.2-kdelibs-dcop.patch
Created attachment 52458 [details, diff] post-3.2.3-kdelibs-dcop.patch
Caleb, please attach an updated ebuilds.
Adding carlo to cc:
Sorry, was a busy weekend for me. Carlo, can you take care of the patches?
Caleb: O.k. with me. It's not time yet, anyways. Just wasn't sure about the last announcement, which mentions the idn issue and wanted to fathom, which patches could make it into 2005.0 (wolf31o2 said the release guys won't wait), so Koon pointed me here.
Created attachment 53344 [details] kdelibs-3.3.2-r6.ebuild
Created attachment 53345 [details, diff] post-3.3.2-kdelibs-idn.patch
corsair, kingtaco: post-3.3.2-kdelibs-idn.patch fixed Bug 81110. I think doing 3.3.2 should suffice, but I thought about marking libidn-0.5.13 stable and additionally with these two bugs it's better to have some more testing going on. Thanks for your help! :)
kingtaco and corsair, please remember just to post your results back to this bug. Nothing can go into the tree until the 16th.
adding cryos as he's our main amd64 kde guy
Created attachment 53349 [details] post-3.3.2-kdelibs-idn.patch-5106.out That idn won't apply: (I'm on ppc64 to test) G5 ~ # emerge kdelibs -u Calculating dependencies ...done! >>> emerge (1 of 1) kde-base/kdelibs-3.3.2-r6 to / >>> md5 src_uri ;-) kdelibs-3.3.2.tar.bz2 >>> Unpacking source... >>> Unpacking kdelibs-3.3.2.tar.bz2 to /var/tmp/portage/kdelibs-3.3.2-r6/work * Applying post-3.3.2-kdelibs-kio.diff ... [ ok ] * Applying post-3.3.2-kdelibs-htmlframes2.patch ... [ ok ] * Applying post-3.3.2-kdelibs-kioslave.patch ... [ ok ] * Applying kdelibs-3.3.2-aspell-dir.patch ... [ ok ] * Applying kdelibs-3.3.2-anchor-fix.patch ... [ ok ] * Applying kde3-dcopidlng.patch ... [ ok ] * Applying post-3.3.2-kdelibs-idn.patch ... * Failed Patch: post-3.3.2-kdelibs-idn.patch! * * Include in your bugreport the contents of: * * /var/tmp/portage/kdelibs-3.3.2-r6/temp/post-3.3.2-kdelibs-idn.patch-5106.out !!! ERROR: kde-base/kdelibs-3.3.2-r6 failed. !!! Function epatch, Line 397, Exitcode 0 !!! Failed Patch: post-3.3.2-kdelibs-idn.patch! !!! If you need support, post the topmost build error, NOT this status message. G5 ~ #
I get the same failure and same post-3.3.2-kdelibs-idn.patch-5106.out as corsair in the previous comment.
Sorry guys. The patch provided by upstream was (at least in part) against branch, not release and I did not notice that epatch omits patches when read permissions are missing, instead to die. Futhermore, I used http://www.shmoo.com/idn/ as test site and it showed me punycode and a warning that the ssl cert doen't match the site, so I thought everything is fine (I mean it is for my KDE 3.3 install, but I have no idea why. *sigh*). #81110 isn't important and changing the diffs from branch to release didn't work (konqueror shows me some odd warning "unknown host www.theshmo"), so I guess there are some other files missing as well, so please test w/o this invalid patch.
Created attachment 53543 [details] kdelibs-3.3.2-r7.ebuild I've recently made a revision bump to 3.3.2-r6.. :-/ That version includes an upstream patch which was already applied to upstream CVS, so it should be save to apply it on all archs. The result is that next kdelibs will be -r7 and not -r6. Sorry for irritation.. -r7 (with post-3.3.2-kdelibs-dcop.patch but NOT post-3.3.2-kdelibs-idn.patch) compiles and works just fine on ppc64. =)
KDE is -r7 ready for general testing? If that is the case please be ready to commit so arches can be called later today when this goes public.
This is now public-> opening. Note from upstream wrt idn: ATTENTION: Please note that post-3.3.2-kdelibs-idn.patch has changed wrt the version that was attached to the preliminary advisory to fix a regression (KDE BR101558) that was discovered this morning. The new version has been attached for your convenience.
<<< kdelibs-3.3.2-r7.ebuild <<< kdelibs-3.2.3-r8.ebuild herds, please go - the idn issue will be handled seperate
kdelibs-3.3.2-r7.ebuild stable on amd64. You want both stable? Just compiling my 3.2 again as I had removed it. It could take a while...
Marcus: On the one hand 3.2.x is keyworded ia64, 3.3.x is not, on the other amd64 is a official supported archtecture and not all users may have updated yet. If multiple arch herds say that they can't support the last two stable major releases, it'd be better to advise ~3.3 for everyone, though.
stable on ppc64
Stable on ppc.
I had to backport the 2005.0 symlink needed by our new profile, but other than that kdelibs-3.2.3-r8.ebuild works just fine and is now marked stable.
Stable on mips.
Stable on SPARC.
Alpha stable.
GLSA 200503-22 hppa, ia64 please remember to mark stable to benifit from the GLSA.
Already stable on hppa
