Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1484111 - (CVE-2017-12159) CVE-2017-12159 keycloak: CSRF token fixation
CVE-2017-12159 keycloak: CSRF token fixation
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20171017,repor...
: Security
Depends On:
Blocks: 1484091
  Show dependency treegraph
 
Reported: 2017-08-22 13:35 EDT by Chess Hazlett
Modified: 2018-08-01 16:56 EDT (History)
17 users (show)

See Also:
Fixed In Version: Keycloak 3.3.0.Final, Keycloak 3.4.0.Final
Doc Type: If docs needed, set a value
Doc Text:
It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session. An attacker could use this flaw to gain access to an authenticated user session, leading to possible 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2904 normal SHIPPED_LIVE Moderate: rh-sso7-keycloak security update 2017-10-17 19:53:00 EDT
Red Hat Product Errata RHSA-2017:2905 normal SHIPPED_LIVE Moderate: rh-sso7-keycloak security update 2017-10-17 19:53:19 EDT
Red Hat Product Errata RHSA-2017:2906 normal SHIPPED_LIVE Moderate: Red Hat Single Sign-On security update 2017-10-17 19:42:35 EDT

  None (edit)
Description Chess Hazlett 2017-08-22 13:35:32 EDT
It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session. An attacker could use this flaw to gain access to an authenticated user session, leading to possible information disclosure or further attacks.

Upstream issue:

https://issues.jboss.org/browse/KEYCLOAK-5234
Comment 2 Chess Hazlett 2017-10-17 12:18:03 EDT
Acknowledgments:

Name: Prapti Mittal
Comment 3 errata-xmlrpc 2017-10-17 15:42:50 EDT
This issue has been addressed in the following products:

  Red Hat Single Sign-On

Via RHSA-2017:2906 https://access.redhat.com/errata/RHSA-2017:2906
Comment 4 errata-xmlrpc 2017-10-17 15:53:51 EDT
This issue has been addressed in the following products:

  Red Hat Single Sign-On 7.1 for RHEL 6

Via RHSA-2017:2904 https://access.redhat.com/errata/RHSA-2017:2904
Comment 5 errata-xmlrpc 2017-10-17 15:54:22 EDT
This issue has been addressed in the following products:

  Red Hat Single Sign-On 7.1 for RHEL 7

Via RHSA-2017:2905 https://access.redhat.com/errata/RHSA-2017:2905
Comment 6 Jason Shepherd 2018-01-09 22:49:32 EST
In version 1.3.1 of keycloak, used by RHMAP, CSRF cookie wasn't added yet. Setting RHMAP as not affected.
https://github.com/keycloak/keycloak/blob/1.3.1.Final/services/src/main/java/org/keycloak/services/resources/WelcomeResource.java

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