Red Hat Inc Keycloak vulnerabilities

CVE-2017-12160 [HIGH] CWE-285 CVE-2017-12160: It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh token pair from the authentication server, permitting indefinite usage in the case of permission revocation. An attacker on an already compromised resource could use this flaw to grant himself continued permissions and possibly conduct further attacks.

CVE-2017-12161 [HIGH] CWE-602 CVE-2017-12161: It was found that keycloak before 3.4.2 final would permit misuse of a client-side /etc/hosts entry It was found that keycloak before 3.4.2 final 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.

CVE-2017-12159 [HIGH] CWE-613 CVE-2017-12159: It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session. An 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.

CVE-2016-8629 [MEDIUM] CWE-284 CVE-2016-8629: Red Hat Keycloak before version 2.4.0 did not correctly check permissions when handling service acco Red Hat Keycloak before version 2.4.0 did not correctly check permissions when handling service account user deletion requests sent to the rest server. An attacker with service account authentication could use this flaw to bypass normal permissions and delete users in a separate realm.

CVE-2017-2585 [MEDIUM] CWE-200 CVE-2017-2585: Red Hat Keycloak before version 2.5.1 has an implementation of HMAC verification for JWS tokens that Red Hat Keycloak before version 2.5.1 has an implementation of HMAC verification for JWS tokens that uses a method that runs in non-constant time, potentially leaving the application vulnerable to timing attacks.

CVE-2017-12158 [MEDIUM] CWE-444 CVE-2017-12158: It was found that Keycloak would accept a HOST header URL in the admin console and use it to determi It was found that Keycloak would accept a HOST header URL in the admin console and use it to determine web resource locations. An attacker could use this flaw against an authenticated user to attain reflected XSS via a malicious server.