Bug 562217 (CVE-2010-0414) - CVE-2010-0414 gnome-screensaver: loses its unlock dialog and keyboard grab sometimes when unplugging monitor
Summary: CVE-2010-0414 gnome-screensaver: loses its unlock dialog and keyboard grab so...
Status: CLOSED ERRATA
Alias: CVE-2010-0414
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=moderate,source=redhat,reporte...
Keywords: Security
: 566774 (view as bug list)
Depends On: 562318 562882
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-05 16:19 UTC by Ray Strode [halfline]
Modified: 2019-06-08 12:55 UTC (History)
7 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-02-25 14:20:23 UTC


Attachments (Terms of Use)
handle monitor topology changes better (2.54 KB, patch)
2010-02-05 16:21 UTC, Ray Strode [halfline]
no flags Details | Diff


External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 609337 None None None Never

Description Ray Strode [halfline] 2010-02-05 16:19:54 UTC
Under certain circumstances it is possible to circumvent the security of screen locking functionality of gnome-screensaver by changing the systems physical monitor configuration.

Steps to reproduce:

1) Lock screen
2) Move mouse to removable monitor
3) hit escape key to cancel unlock dialog
4) move mouse to bring up unlock dialog on new head
5) unplug monitor
6) quickly hit keys on the keyboard

At this point gnome-screensaver will either crash, or show a black screen.  If it shows a black screen then hitting "alt-f2" and then typing "pkill -f gnome-screensaver" will bring you to the session.

Comment 1 Ray Strode [halfline] 2010-02-05 16:21:20 UTC
Created attachment 389117 [details]
handle monitor topology changes better

This addresses the issue by fixing the code paths that handle a monitor disappearing.

Comment 2 Ray Strode [halfline] 2010-02-05 22:16:21 UTC
Note the only stable gnome release this affects is 2.28.

The code that caused this issue went into gnome-screensaver some time ago during the 2.24 devel cycle:

http://git.gnome.org/browse/gnome-screensaver/commit/?id=f6d3defdc

But we didn't get autoconfiguration of hotplugged monitors until gnome 2.28's devel cycle:

http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=be513b3

Which is a prerequisite for triggering this bug.

Comment 3 Vincent Danen 2010-02-05 22:27:50 UTC
This has been given the name CVE-2010-0414.

Comment 6 Vincent Danen 2010-02-08 16:20:43 UTC
Embargo is lifted and this issue is public now.

Comment 9 Fedora Update System 2010-02-09 04:59:39 UTC
gnome-screensaver-2.28.2-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Ray Strode [halfline] 2010-02-19 19:53:16 UTC
*** Bug 566774 has been marked as a duplicate of this bug. ***


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