1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

An Easy But Serious Screensaver Security Problem In X.Org

X.Org

Published on 18 January 2012 10:52 PM EST
Written by Michael Larabel in X.Org
24 Comments

I've been alerted this afternoon that there's an outstanding security vulnerability within the current X.Org Server that's receiving little attention. This active vulnerability could allow anyone with physical access to your system to easily bypass the desktop's screen lock regardless of your desktop environment.

A blog post at aeroxteam.fr initially uncovered and detailed this apparent vulnerability. A commit to XKB for X.Org Server 1.11 adds a few debug key actions for grabs and the window tree. One of the four new XKB actions allowed is killing clients with active grabs, which is what most (or perhaps all) desktop environment screensavers rely upon for their screensaver lock -- just ensuring they have the top window and are catching all input events. One of the other four options is unleashing all active grabs. While a debugging feature, both of these are appearing by default in some of the leading Linux distributions.

CTRL+ALT+F10 by default in the xorg-server will now ungrab all currently active grabs and CTRL+ALT+F11 will kill clients with active grabs, if you're running a stock XKB map. (Additionally as part of this commit, CTRL+ALT+F9 will print active grabs to the log file and CTRL+ALT+F12 will dump the current window tree to the log file). Another option is using CTRL+ALT+Keypad-Multiply for this bug. This is on X.Org Server 1.11 and it also is appearing that way in the Git for what will become X.Org Server 1.12 this March. This code was previously in the X.Org Server tree years ago as a debugging utility too, but back then it was disabled by default and only could be enabled if set within the xorg.conf.

As mentioned in the aforelinked blog post by "Gu1", this new debugging functionality isn't clearly documented nor can it even be disabled easily. To disable this screensaver workaround, you must edit the XKB keyboard mapping configuration manually to remove XF86Ungrab and XF86ClearGrab mentions. The commit was authored by Daniel Stone and sent into the xserver Git this past June.

An Easy But Serious Screensaver Security Problem In X.Org
Working on X while drinking Phoronix beer... A bad combination? XDC2011 Chicago.

X.Org Server 1.11+ users are affected, which is currently shipping in Fedora 16, is to be shipping in Ubuntu 12.04 LTS, Debian unstable, Arch Linux, Gentoo, and others. X.Org Server 1.11 was released last September prior to XDC2011 Chicago. GNOME 3.x and KDE 4.x are among the desktop environments affected by this security snafu.

Embedded below is an iPhone video I quickly recorded tonight after carrying out a clean install of Debian "Wheezy" on one of the Phoronix systems. Wheezy is currently using X.Org Server 1.11.1 and tested was the GNOME Shell. No package or configuration changes were made to the Debian Linux installation. After locking the screen of the Debian desktop, it was simply a matter of pressing the CTRL+ALT+Keypad-Multiply combination and you're back at the desktop without inputting any password.


In summary, if your Linux distribution is using X.Org Server 1.11+ -- it's been out there for four months ago while the commit introducing the potential problem has been in Git since last June -- (you can find out by running X -version) and the XKB mapping has the standard debugging features, you may be at risk of your screensaver lock being useless if anyone were to just hit a simple keyboard combination, since then they can be brought to your desktop with full access and no password being needed. This problem wouldn't be limited to Linux but any operating system using the modern (v1.11+) X.Org Server, such as the *BSDs and Solaris.

At least the Wayland Display Server hopes to have a proper screensaver implementation...

Update: This issue is additionally being confirmed now within the forums.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux Hardware Reviews
  1. Acer B286HK: A 28-inch UHD LED 4K Monitor For As Low As $350
  2. Intel Xeon E5-1680 v3 & E5-2687W v3 Compared To The Core i7 5960X On Linux
  3. Intel 120GB 530 Series SSD Linux Performance
  4. Btrfs/EXT4/XFS/F2FS RAID 0/1/5/6/10 Linux Benchmarks On Four SSDs
Latest Linux Articles
  1. Mesa Git Yields Performance Improvements For Newer AMD GPUs
  2. Apple OS X 10.10 vs. Ubuntu 14.10 Performance
  3. Mesa 10.5-devel Brings Some Intel Haswell HD Graphics Changes Over Mesa 10.3
  4. NVIDIA vs. Nouveau Drivers With Linux 3.18 + Mesa 10.4-devel
Latest Linux News
  1. NVIDIA Posts Tegra Gallium3D Patch For K1+ Support
  2. Ubuntu 14.10 MacBook Air Tests With Linux 3.18, Mesa 10.5
  3. AMD Richland APU Support Added To Coreboot
  4. 2014 Holiday Shopping Reminder, Happy Thanksgiving
  5. Python 3 Support Added To The GNOME Shell
  6. ReactOS Lands Its New Explorer Shell
  7. Weston's IVI Shell Sees New Version
  8. IMP Launches As Another Open-Source Computer Attempt
  9. Git 2.2.0 Released With 550+ Changes
  10. GNOME 3.15.2 Released
Latest Forum Discussions
  1. Updated and Optimized Ubuntu Free Graphics Drivers
  2. Hurrican SDL Port
  3. Roadmap to Catalyst 14.10 ?
  4. how to configure module phoromatic ?
  5. PulseAudio 6.0 Is Coming & Other Linux Audio Plans For The Future
  6. Debian Developer Resigns From The Systemd Maintainership Team
  7. Cant get working Kaveri APU - A10-7850k
  8. Script for Fan Speed Control