Summary: | kde-base/kdebase kcheckpass local root vulnerability | ||||||
---|---|---|---|---|---|---|---|
Product: | Gentoo Security | Reporter: | Sune Kloppenborg Jeppesen (RETIRED) <jaervosz> | ||||
Component: | Vulnerabilities | Assignee: | Gentoo Security <security> | ||||
Status: | RESOLVED WORKSFORME | ||||||
Severity: | major | CC: | caleb, carlo, dercorny | ||||
Priority: | High | ||||||
Version: | unspecified | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | B1? [preebuild] jaervosz CONFIDENTIAL 20050905 | ||||||
Package list: | Runtime testing required: | --- | |||||
Attachments: |
|
Description
Sune Kloppenborg Jeppesen (RETIRED)
![]() Created attachment 67134 [details, diff]
post-3.4.2-kdebase-kcheckpass.diff
KDE please attach updated ebuilds. Do NOT commit to Portage. "In order for an exploit to succeed, the directory /var/lock has to be writeable for a user that is allowed to invoke kcheckpass." $ ls -ld /var/lock drwxrwxr-x 3 root uucp 4096 ao "In order for an exploit to succeed, the directory /var/lock has to be writeable for a user that is allowed to invoke kcheckpass." $ ls -ld /var/lock drwxrwxr-x 3 root uucp 4096 aoĆ» 29 09:18 /var/lock Not sure we are affected... Perhaps not in standard configuration, that was why I rated it B1? Hm. Changing /var/lock ownership is not a "configuration" option for kcheckpass, it's a serious change. I would say Gentoo is not affected by this vulnerability as it ships /var/lock with the correct permissions... Otherwise all packages using tmpfiles would be "vulnerable to symlink attacks" in case someone plays with /tmp permissions... I would close this one as WORKSFORME. KDE if you agree we'll close this one. fyi: My Gentoo box is (sort of) dead atm., so I can't build/test anything unless I have replaced it, but I think this is a non-issue, too. Thx Carlo -> Closing. opening *** Bug 105997 has been marked as a duplicate of this bug. *** |