Bug 145381 - CAN-2005-0078 password bypass in kde screensaver
CAN-2005-0078 password bypass in kde screensaver
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kdebase (Show other bugs)
2.1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
impact=moderate,embargoed=20050126
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-01-17 16:38 EST by Josh Bressers
Modified: 2007-11-30 17:06 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-02-10 11:43:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Proposed patch for this issue. (1.74 KB, patch)
2005-01-17 16:38 EST, Josh Bressers
no flags Details | Diff

  None (edit)
Description Josh Bressers 2005-01-17 16:38:10 EST
Created attachment 109890 [details]
Proposed patch for this issue.
Comment 1 Josh Bressers 2005-01-17 16:38:10 EST
Debian reported this to vendor-sec on 2005-01-16

--------------------------------------
This only affects KDE older than 3.0.5
--------------------------------------

Raphaël Enrici discovered that the KDE screensaver can crash under
certain local circumstances.  This can be exploited by an attacker
with physical access to the workstation to take over the desktop
session.

When kscreensaver has locked the screen and the user disappears
getpwuid() returns NULL which is not taken care of.  As a result
the screensaver will crash.  In a version more recent than 2.2
the screensaver and locker are differnt processes, but the locker
has the same issues, until it was fixed in November 2002 and made
it into KDE 3.0.5.

For older versions of KDE the attached patch or a forward port will
fix this problem.


This issue only affects RHEL2.1
Comment 2 Ngo Than 2005-01-20 09:40:07 EST
it's fixed in kdebase-2.2.2-14
Comment 3 Mark J. Cox (Product Security) 2005-01-28 03:53:08 EST
Now public
Comment 4 Josh Bressers 2005-02-10 11:43:13 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2005-009.html

Note You need to log in before you can comment on or make changes to this bug.