Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1391126 - (CVE-2016-1000002) CVE-2016-1000002 gdm: Information leak before screen lock
CVE-2016-1000002 gdm: Information leak before screen lock
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20160602,reported=2...
: Security
Depends On: 713640
Blocks:
  Show dependency treegraph
 
Reported: 2016-11-02 11:35 EDT by Adam Mariš
Modified: 2018-03-16 10:58 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-02 11:36:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2016-11-02 11:35:37 EDT
Gnome GDM 3.14.2 and possibly later are vulnerable to an information disclosure vulnerability, specifically when a laptop screen is closed to trigger the screen lock, and the lid is then re-opened the previous contents of the screen are visible for approx. 1 second, which is long enough to take a picture or video record it before the lock screen kicks in.
Comment 1 Tim Jackson 2017-01-12 02:47:30 EST
Why WONTFIX?
Comment 2 Laurent Bigonville 2017-01-12 03:20:32 EST
Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=753678
Comment 3 Adam Mariš 2017-01-12 11:10:36 EST
(In reply to Tim Jackson from comment #1)
> Why WONTFIX?

Requirement for physical access of the attacker and limited information disclosure as the only impact makes this a Low impact bug, hence WONTFIX.
Comment 4 Adam Mariš 2017-01-12 11:12:15 EST
Statement:

Red Hat Product Security has rated this issue as having Low security
impact. This issue is not currently planned to be addressed in future
updates. For additional information, refer to the Issue Severity
Classification: https://access.redhat.com/security/updates/classification/.

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