After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 789638 - Gnome Shell Allows for Unauthenticated logon from lock screen.
Gnome Shell Allows for Unauthenticated logon from lock screen.
Status: RESOLVED DUPLICATE of bug 783779
Product: gnome-shell
Classification: Core
Component: lock-screen
3.24.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-10-30 05:32 UTC by James Pack
Modified: 2017-11-01 13:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description James Pack 2017-10-30 05:32:03 UTC
I am running Ubuntu GNOME version 17.04.

After logging on if I lock the screen and then try to log back on I am prompted with the unlock dialog as expected. However if I click the link at the bottom that says "Login as another user" the system unlocks *Without* entering credentials.
Comment 1 André Klapper 2017-10-30 18:52:30 UTC
Thanks for reporting this.
Which gnome-shell version is this about? 
How many other user accounts are configured?
Comment 2 Florian Müllner 2017-10-30 18:57:45 UTC
Also:
 - is the session actually unlocked, or does gnome-shell crash?
 - are you using GDM, or are there patches to allow screen locking
   with LightDM?
Comment 3 James Pack 2017-10-31 02:36:16 UTC
I will try to address all of the questions as best I can.

1. Output of gnome-shell --version:  GNOME Shell 3.24.2
2. I am the only user configured on the system
3. The session is unlocked as far as I can tell. I am taken back to my desktop and it does not appear to crash (ie. no crash report prompt or screen flashing)
4. I am using GDM3. The output of gdm3 --version: GDM 3.24.1
5. I am not sure about patches for lightdm but I don't think it is in play here.
Comment 4 James Pack 2017-10-31 02:58:08 UTC
After some additional testing, it appears that this behavior is only present when automatic login is enabled. So perhaps the shell is doing the right thing? Maybe. Not sure what happens if there is more than one user.
Comment 5 Ray Strode [halfline] 2017-11-01 13:51:49 UTC
This actually is a bug, which was assigned CVE-2017-12164.

See https://mail.gnome.org/archives/distributor-list/2017-September/msg00003.html

*** This bug has been marked as a duplicate of bug 783779 ***