First published: Wed Feb 01 2012(Updated: )
<a href="https://bugs.gentoo.org/show_bug.cgi?id=401645">https://bugs.gentoo.org/show_bug.cgi?id=401645</a> Jeroen Roovers 2012-01-31 17:23:28 UTC 1) In a terminal, I run `slock & sleep 5; <some X app>' 2) After about 10 seconds, I press some keys that slock would interpret as a password. 3a) It does not allow me to use <some X app> - all keyboard controls are captured. 3b) Pointer device input is blocked - <some X app> cannot be controlled through the mouse. 4) Entering the correct password unlocks the screen and makes <some X app> focused and in the foreground. The only harm I see here is a possible unwanted disclosure of the information that <some X app> happens to display at the time, but it's a vulnerability sure enough.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
slock | =0.9 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-1620 is classified as a high-severity vulnerability due to its potential to allow unauthorized access.
To fix CVE-2012-1620, update slock to a version newer than 0.9 that addresses this security issue.
Users running slock version 0.9 are affected by CVE-2012-1620.
Linux systems that utilize slock version 0.9 are vulnerable to CVE-2012-1620.
Exploits for CVE-2012-1620 can allow an attacker to bypass the lock screen through crafted input.