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
Acknowledgments: Name: Prapti Mittal
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
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
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
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