Bug 1305770

Summary:	libgnome: Enrolling fingerprint requires no password
Product:	[Other] Security Response	Reporter:	Adam Mariš <amaris>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	bnocera, mattdm, puiterwijk, rstrode, security-response-team
Target Milestone:	---	Keywords:	Reopened, Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-08 02:48:15 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1333882
Bug Blocks:	1305771

Description Adam Mariš 2016-02-09 08:27:43 UTC

It was reported that in Gnome 3, it is possible to enroll a new fingerprint for login authentication (which can also be used for sudo in some configurations), without having to enter the owner's password. Attacker can enroll his own fingerprint when the owner leaves their laptop unlocked for a minute, meaning he can also enter the laptop later if its locked.

Comment 3 Adam Mariš 2016-05-06 14:31:37 UTC

Upstream bug:

https://bugs.freedesktop.org/show_bug.cgi?id=89407

Note that this behavior can be changed in fprintd PolicyKit settings in /usr/share/polkit-1/actions/net.reactivated.fprint.device.policy

Comment 4 Adam Mariš 2016-05-06 14:32:31 UTC

Created fprintd tracking bugs for this issue:

Affects: fedora-all [bug 1333882]

Comment 7 Adam Mariš 2016-05-09 14:55:55 UTC

This issue has been reported as far back as 2011:

https://bugzilla.gnome.org/show_bug.cgi?id=651196

Comment 8 Patrick Uiterwijk 2016-08-06 07:53:31 UTC

Note that the GNOME bug says that the decision is up to the distribution policy, but it seems that the distribution policy for Fedora apparantly does not require authentication.
So for Fedora, this is still a bug.