National Vulnerability Database

National Vulnerability Database

National Vulnerability

Search Results (Refine Search)

Search Parameters:
  • CPE Product Version: cpe:/a:redhat:keycloak:1.9.1
There are 14 matching records.
Vuln ID Summary CVSS Severity

It was found that keycloak before version 8.0.0 exposes internal adapter endpoints in org.keycloak.constants.AdapterConstants, which can be invoked via a specially-crafted URL. This vulnerability could allow an attacker to access unauthorized information.

Published: January 08, 2020; 10:15:11 AM -05:00
V3.1: 4.3 MEDIUM
    V2: 4.0 MEDIUM

A flaw was found in keycloack before version 8.0.0. The owner of '' domain can setup mail server on this domain and knowing only name of a client can reset password and then log in. For example, for client name 'test' the email address will be ''.

Published: January 07, 2020; 12:15:11 PM -05:00
V3.1: 9.1 CRITICAL
    V2: 6.4 MEDIUM

A flaw was found in the Keycloak REST API before version 8.0.0 where it would permit user access from a realm the user was not configured. An authenticated attacker with knowledge of a user id could use this flaw to access unauthorized information or to carry out further attacks.

Published: October 15, 2019; 03:15:11 PM -04:00
V3.1: 7.5 HIGH
    V2: 6.0 MEDIUM

It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures. If an attacker modifies the SAML Response and removes the <Signature> sections, the message is still accepted, and the message can be modified. An attacker could use this flaw to impersonate other users and gain access to sensitive information.

Published: August 14, 2019; 01:15:11 PM -04:00
V3.0: 8.1 HIGH
    V2: 5.5 MEDIUM

It was found that Keycloak's account console, up to 6.0.1, did not perform adequate header checks in some requests. An attacker could use this flaw to trick an authenticated user into performing operations via request from an untrusted domain.

Published: August 14, 2019; 01:15:11 PM -04:00
V3.0: 8.8 HIGH
    V2: 6.8 MEDIUM

A vulnerability was found in keycloak before 6.0.2. The X.509 authenticator supports the verification of client certificates through the CRL, where the CRL list can be obtained from the URL provided in the certificate itself (CDP) or through the separately configured path. The CRL are often available over the network through unsecured protocols ('http' or 'ldap') and hence the caller should verify the signature and possibly the certification path. Keycloak currently doesn't validate signatures on CRL, which can result in a possibility of various attacks like man-in-the-middle.

Published: June 12, 2019; 10:29:04 AM -04:00
V3.0: 4.8 MEDIUM
    V2: 5.8 MEDIUM

It was found that Keycloak's Node.js adapter before version 4.8.3 did not properly verify the web token received from the server in its backchannel logout . An attacker with local access could use this to construct a malicious web token setting an NBF parameter that could prevent user access indefinitely.

Published: June 12, 2019; 10:29:02 AM -04:00
V3.0: 5.5 MEDIUM
    V2: 2.1 LOW

Keycloak up to version 6.0.0 allows the end user token (access or id token JWT) to be used as the session cookie for browser sessions for OIDC. As a result an attacker with access to service provider backend could hijack user?s browser session.

Published: April 24, 2019; 12:29:02 PM -04:00
V3.0: 3.8 LOW
    V2: 5.5 MEDIUM

The SAML broker consumer endpoint in Keycloak before version 4.6.0.Final ignores expiration conditions on SAML assertions. An attacker can exploit this vulnerability to perform a replay attack.

Published: November 30, 2018; 08:29:00 AM -05:00
V3.0: 8.1 HIGH
    V2: 6.8 MEDIUM

It was found that the keycloak before 2.3.0 did not implement authentication flow correctly. An attacker could use this flaw to construct a phishing URL, from which he could hijack the user's session. This could lead to information disclosure, or permit further possible attacks.

Published: August 01, 2018; 01:29:00 PM -04:00
V3.0: 8.1 HIGH
    V2: 5.8 MEDIUM

It was found that when Keycloak before 2.5.5 receives a Logout request with a Extensions in the middle of the request, the SAMLSloRequestParser.parse() method ends in a infinite loop. An attacker could use this flaw to conduct denial of service attacks.

Published: July 27, 2018; 02:29:01 PM -04:00
V3.0: 7.5 HIGH
    V2: 5.0 MEDIUM

It was found that while parsing the SAML messages the StaxParserUtil class of keycloak before 2.5.1 replaces special strings for obtaining attribute values with system property. This could allow an attacker to determine values of system properties at the attacked system by formatting the SAML request ID field to be the chosen system property which could be obtained in the "InResponseTo" field in the response.

Published: July 26, 2018; 01:29:00 PM -04:00
V3.0: 6.5 MEDIUM
    V2: 4.0 MEDIUM

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.

Published: March 12, 2018; 11:29:00 AM -04:00
V3.0: 5.9 MEDIUM
    V2: 4.3 MEDIUM

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.

Published: March 12, 2018; 11:29:00 AM -04:00
V3.0: 6.5 MEDIUM
    V2: 5.5 MEDIUM