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. A Walkthrough Of The New 32 System Open-Source Linux Benchmarking Test Farm
  2. Habey MITX-6771: Mini-ITX Board With Quad-Core J1900 Bay Trail
  3. OCZ Vector 150 SSD On Linux
  4. Noctua i4 CPU Cooler: Great For Cooling High-End LGA-2011v3 CPUs
Latest Linux Articles
  1. 17-Way Linux Graphics Card Comparison With Civilization Beyond Earth
  2. AMD Kaveri: Open-Source Radeon Gallium3D vs. Catalyst 14.12 Omega Driver
  3. 12-Way AMD Catalyst 14.12 vs. NVIDIA 346 Series Linux GPU Comparison
  4. AMD Catalyst 14.12 Omega Driver Brings Mixed Results For Linux Users
Latest Linux News
  1. Server-Side XCB Is Being Discussed For The X.Org Server
  2. Adreno A4xx Rendering With Freedreno Takes Shape
  3. Linux 3.19-rc1 Kernel Released Ahead Of Schedule
  4. Civilization: Beyond Earth Linux GPU/Driver Benchmarks
  5. X.Org Server 1.16.3 Released To Fix Security Issues
  6. Linux 3.19 Merge Window Closes Ahead Of Schedule
  7. MIPS R6 Architecture Now Supported By GCC
  8. LowRISC To Feature Tagged Memory & Minion Cores
  9. Intel Skylake Audio Support For Linux 3.19
  10. After 10+ Years, NetworkManager Reaches v1.0
Latest Forum Discussions
  1. Speeding up systemd networking service
  2. Need some hand holding with upgrading xserver
  3. FPS capped on Linux (AMD fglrx drivers)
  4. Are there an app using HSA ?
  5. The New SuperTuxKart Looks Better, But Can Cause GPU/Driver Problems
  6. XLennart: A Game For Systemd Haters With Nothing Better To Do
  7. Updated and Optimized Ubuntu Free Graphics Drivers
  8. Debian init discussion in Phoenix Wright format