Bug 1484564 – CVE-2017-12161 keycloak: reset password token disclosure

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1484564 - (CVE-2017-12161) CVE-2017-12161 keycloak: reset password token disclosure

Summary:	CVE-2017-12161 keycloak: reset password token disclosure

Status:	NEW

Aliases:	CVE-2017-12161

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=moderate,public=20171214,repor...
Keywords:	Security

Duplicates:	CVE-2017-1000500 (view as bug list)
Depends On:
Blocks:	1484091 1533321
	Show dependency tree / graph

Reported:	2017-08-23 17:04 EDT by Chess Hazlett
Modified:	2018-02-15 18:34 EST (History)
CC List:	18 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:	it was found that keycloak would permit misuse of a client-side /etc/hosts entry to spoof a URL in a password reset request. An attacker could use this flaw to craft a malicious password reset request and gain a valid reset token, leading to information disclosure or further attacks.
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Chess Hazlett 2017-08-23 17:04:13 EDT

https://issues.jboss.org/browse/KEYCLOAK-5299

Comment 1 Jason Shepherd 2018-01-10 00:03:39 EST

Attack relies on compromising /etc/hosts file and tricking user into clicking reset password link with invalid URL. Wontfix for RHMAP-4

Comment 2 Jason Shepherd 2018-02-15 18:31:40 EST

*** Bug 1533319 has been marked as a duplicate of this bug. ***

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