Keycloak Red Hat Keycloak

Do you want an email whenever new security vulnerabilities are reported in Red Hat Keycloak?

By the Year

In 2021 there have been 11 vulnerabilities in Red Hat Keycloak with an average score of 6.2 out of ten. Last year Keycloak had 21 security vulnerabilities published. Right now, Keycloak is on track to have less security vulnerabilities in 2021 than it did last year. Last year, the average CVE base score was greater by 0.03

Year Vulnerabilities Average Score
2021 11 6.19
2020 21 6.22
2019 8 7.08
2018 6 6.33

It may take a day or so for new Keycloak vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Red Hat Keycloak Security Vulnerabilities

A flaw was found in keycloak-model-infinispan in keycloak versions before 14.0.0 where authenticationSessions map in RootAuthenticationSessionEntity grows boundlessly

CVE-2021-3637 7.5 - High - July 09, 2021

A flaw was found in keycloak-model-infinispan in keycloak versions before 14.0.0 where authenticationSessions map in RootAuthenticationSessionEntity grows boundlessly which could lead to a DoS attack.

Allocation of Resources Without Limits or Throttling

A flaw was found in keycloak in versions before 13.0.0

CVE-2021-20195 9.6 - Critical - May 28, 2021

A flaw was found in keycloak in versions before 13.0.0. A Self Stored XSS attack vector escalating to a complete account takeover is possible due to user-supplied data fields not being properly encoded and Javascript code being used to process the data. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Improper Input Validation

A flaw was found in Keycloak before version 12.0.0 where it is possible to update the user's metadata attributes using Account REST API

CVE-2020-27826 4.2 - Medium - May 28, 2021

A flaw was found in Keycloak before version 12.0.0 where it is possible to update the user's metadata attributes using Account REST API. This flaw allows an attacker to change its own NameID attribute to impersonate the admin user for any particular application.

Execution with Unnecessary Privileges

A flaw was found in keycloak

CVE-2021-20202 7.3 - High - May 12, 2021

A flaw was found in keycloak. Directories can be created prior to the Java process creating them in the temporary directory, but with wider user permissions, allowing the attacker to have access to the contents that keycloak stores in this directory. The highest threat from this vulnerability is to data confidentiality and integrity.

Insecure Temporary File

A flaw was found in keycloak

CVE-2021-20222 7.5 - High - March 23, 2021

A flaw was found in keycloak. The new account console in keycloak can allow malicious code to be executed using the referrer URL. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

Improper Input Validation

A flaw was found in Keycloak 12.0.0 where re-authentication does not occur while updating the password

CVE-2021-20262 6.8 - Medium - March 09, 2021

A flaw was found in Keycloak 12.0.0 where re-authentication does not occur while updating the password. This flaw allows an attacker to take over an account if they can obtain temporary, physical access to a users browser. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.

Missing Authentication for Critical Function

A flaw was found in keycloak in versions prior to 13.0.0

CVE-2020-27838 6.5 - Medium - March 08, 2021

A flaw was found in keycloak in versions prior to 13.0.0. The client registration endpoint allows fetching information about PUBLIC clients (like client secret) without authentication which could be an issue if the same PUBLIC client changed to CONFIDENTIAL later. The highest threat from this vulnerability is to data confidentiality.

authentification

A vulnerability was found in all versions of keycloak, where on using lower case HTTP headers (via cURL) we can bypass our Gatekeeper

CVE-2020-14359 7.3 - High - February 23, 2021

A vulnerability was found in all versions of keycloak, where on using lower case HTTP headers (via cURL) we can bypass our Gatekeeper. Lower case headers are also accepted by some webservers (e.g. Jetty). This means there is no protection when we put a Gatekeeper in front of a Jetty server and use lowercase headers.

Authentication Bypass by Primary Weakness

A flaw was found in Keycloak 7.0.1

CVE-2020-1717 2.7 - Low - February 11, 2021

A flaw was found in Keycloak 7.0.1. A logged in user can do an account email enumeration attack.

Generation of Error Message Containing Sensitive Information

A vulnerability was found in keycloak in the way that the OIDC logout endpoint does not have CSRF protection

CVE-2020-10734 3.3 - Low - February 11, 2021

A vulnerability was found in keycloak in the way that the OIDC logout endpoint does not have CSRF protection. Versions shipped with Red Hat Fuse 7, Red Hat Single Sign-on 7, and Red Hat Openshift Application Runtimes are believed to be vulnerable.

Session Riding

A flaw was found in keycloak before version 13.0.0

CVE-2020-1725 5.4 - Medium - January 28, 2021

A flaw was found in keycloak before version 13.0.0. In some scenarios a user still has access to a resource after changing the role mappings in Keycloak and after expiration of the previous access token.

AuthZ

A flaw was found in Keycloak before 13.0.0 where an external identity provider, after successful authentication, redirects to a Keycloak endpoint

CVE-2020-14302 4.9 - Medium - December 15, 2020

A flaw was found in Keycloak before 13.0.0 where an external identity provider, after successful authentication, redirects to a Keycloak endpoint that accepts multiple invocations with the use of the same "state" parameter. This flaw allows a malicious user to perform replay attacks.

Authentication Bypass by Capture-replay

A flaw was found in Keycloak before 13.0.0

CVE-2020-10770 5.3 - Medium - December 15, 2020

A flaw was found in Keycloak before 13.0.0, where it is possible to force the server to call out an unverified URL using the OIDC parameter request_uri. This flaw allows an attacker to use this parameter to execute a Server-side request forgery (SSRF) attack.

Open Redirect

A flaw was found in Keycloak before version 12.0.0, where it is possible to add unsafe schemes for the redirect_uri parameter

CVE-2020-10776 4.8 - Medium - November 17, 2020

A flaw was found in Keycloak before version 12.0.0, where it is possible to add unsafe schemes for the redirect_uri parameter. This flaw allows an attacker to perform a Cross-site scripting attack.

XSS

It was found that Keycloak before version 12.0.0 would permit a user with only view-profile role to manage the resources in the new account console

CVE-2020-14389 8.1 - High - November 17, 2020

It was found that Keycloak before version 12.0.0 would permit a user with only view-profile role to manage the resources in the new account console, allowing access and modification of data the user was not intended to have.

Improper Privilege Management

A vulnerability was found in keycloak, where path traversal using URL-encoded path segments in the request is possible

CVE-2020-14366 7.5 - High - November 09, 2020

A vulnerability was found in keycloak, where path traversal using URL-encoded path segments in the request is possible because the resources endpoint applies a transformation of the url path to the file path. Only few specific folder hierarchies can be exposed by this flaw

Directory traversal

A flaw was found in all versions of Keycloak before 10.0.0, where the NodeJS adapter did not support the verify-token-audience

CVE-2020-1694 4.9 - Medium - September 16, 2020

A flaw was found in all versions of Keycloak before 10.0.0, where the NodeJS adapter did not support the verify-token-audience. This flaw results in some users having access to sensitive information outside of their permissions.

Incorrect Permission Assignment for Critical Resource

A vulnerability was found in Keycloak before 11.0.1 where DoS attack is possible by sending twenty requests simultaneously to the specified keycloak server, all with a Content-Length header value

CVE-2020-10758 7.5 - High - September 16, 2020

A vulnerability was found in Keycloak before 11.0.1 where DoS attack is possible by sending twenty requests simultaneously to the specified keycloak server, all with a Content-Length header value that exceeds the actual byte count of the request body.

Allocation of Resources Without Limits or Throttling

A vulnerability was found in Keycloak before 9.0.2, where every Authorization URL

CVE-2020-1727 5.4 - Medium - June 22, 2020

A vulnerability was found in Keycloak before 9.0.2, where every Authorization URL that points to an IDP server lacks proper input validation as it allows a wide range of characters. This flaw allows a malicious to craft deep links that introduce further attack scenarios on affected clients.

Improper Input Validation

A flaw was found in Keycloak in versions before 10.0.0

CVE-2020-1758 5.9 - Medium - May 15, 2020

A flaw was found in Keycloak in versions before 10.0.0, where it does not perform the TLS hostname verification while sending emails using the SMTP server. This flaw allows an attacker to perform a man-in-the-middle (MITM) attack.

Improper Certificate Validation

A flaw was found in Keycloak before version 11.0.0, where the code base contains usages of ObjectInputStream without type checks

CVE-2020-1714 8.8 - High - May 13, 2020

A flaw was found in Keycloak before version 11.0.0, where the code base contains usages of ObjectInputStream without type checks. This flaw allows an attacker to inject arbitrarily serialized Java Objects, which would then get deserialized in a privileged context and potentially lead to remote code execution.

Improper Input Validation

A flaw was found in the reset credential flow in all Keycloak versions before 8.0.0

CVE-2020-1718 8.8 - High - May 12, 2020

A flaw was found in the reset credential flow in all Keycloak versions before 8.0.0. This flaw allows an attacker to gain unauthorized access to the application.

authentification

A flaw was found in Keycloak in versions before 9.0.2

CVE-2020-1724 4.3 - Medium - May 11, 2020

A flaw was found in Keycloak in versions before 9.0.2. This flaw allows a malicious user that is currently logged in, to see the personal information of a previously logged out user in the account manager section.

Insufficient Session Expiration

A flaw was found in keycloak in versions before 9.0.0

CVE-2020-1698 5.5 - Medium - May 11, 2020

A flaw was found in keycloak in versions before 9.0.0. A logged exception in the HttpMethod class may leak the password given as parameter. The highest threat from this vulnerability is to data confidentiality.

Information Disclosure

A flaw was found in Keycloaks user-managed access interface, where it would permit a script to be set in the UMA policy

CVE-2019-10169 7.2 - High - May 08, 2020

A flaw was found in Keycloaks user-managed access interface, where it would permit a script to be set in the UMA policy. This flaw allows an authenticated attacker with UMA permissions to configure a malicious script to trigger and execute arbitrary code with the permissions of the user running application.

Improper Privilege Management

A flaw was found in the Keycloak admin console, where the realm management interface permits a script to be set via the policy

CVE-2019-10170 7.2 - High - May 08, 2020

A flaw was found in the Keycloak admin console, where the realm management interface permits a script to be set via the policy. This flaw allows an attacker with authenticated user and realm management permissions to configure a malicious script to trigger and execute arbitrary code with the permissions of the application user.

Improper Privilege Management

A flaw was found in Keycloak version 8.0.2 and 9.0.0, and was fixed in Keycloak version 9.0.1, where a malicious user registers as oneself

CVE-2020-10686 4.7 - Medium - May 04, 2020

A flaw was found in Keycloak version 8.0.2 and 9.0.0, and was fixed in Keycloak version 9.0.1, where a malicious user registers as oneself. The attacker could then use the remove devices form to post different credential IDs and possibly remove MFA devices for other users.

AuthZ

A vulnerability was found in all versions of Keycloak where

CVE-2020-1728 5.4 - Medium - April 06, 2020

A vulnerability was found in all versions of Keycloak where, the pages on the Admin Console area of the application are completely missing general HTTP security headers in HTTP-responses. This does not directly lead to a security issue, yet it might aid attackers in their efforts to exploit other problems. The flaws unnecessarily make the servers more prone to Clickjacking, channel downgrade attacks and other similar client-based attack vectors.

Clickjacking

A flaw was found in keycloak before version 9.0.1

CVE-2020-1744 5.6 - Medium - March 24, 2020

A flaw was found in keycloak before version 9.0.1. When configuring an Conditional OTP Authentication Flow as a post login flow of an IDP, the failure login events for OTP are not being sent to the brute force protection event queue. So BruteForceProtector does not handle this events.

Information Disclosure

It was found in all keycloak versions before 9.0.0

CVE-2020-1697 5.4 - Medium - February 10, 2020

It was found in all keycloak versions before 9.0.0 that links to external applications (Application Links) in the admin console are not validated properly and could allow Stored XSS attacks. An authed malicious user could create URLs to trick users in other realms, and possibly conduct further attacks.

XSS

It was found that keycloak before version 8.0.0 exposes internal adapter endpoints in org.keycloak.constants.AdapterConstants, which can be invoked

CVE-2019-14820 4.3 - Medium - January 08, 2020

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.

Information Disclosure

A flaw was found in keycloack before version 8.0.0

CVE-2019-14837 9.1 - Critical - January 07, 2020

A flaw was found in keycloack before version 8.0.0. The owner of 'placeholder.org' 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 'service-account-test@placeholder.org'.

Use of Hard-coded Credentials

A vulnerability was found in keycloak 7.x, when keycloak is configured with LDAP user federation and StartTLS is used instead of SSL/TLS

CVE-2019-14910 9.8 - Critical - December 05, 2019

A vulnerability was found in keycloak 7.x, when keycloak is configured with LDAP user federation and StartTLS is used instead of SSL/TLS from the LDAP server (ldaps), in this case user authentication succeeds even if invalid password has entered.

authentification

A vulnerability was found in Keycloak 7.x where the user federation LDAP bind type is none (LDAP anonymous bind)

CVE-2019-14909 8.3 - High - December 04, 2019

A vulnerability was found in Keycloak 7.x where the user federation LDAP bind type is none (LDAP anonymous bind), any password, invalid or valid will be accepted.

authentification

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

CVE-2019-14832 7.5 - High - October 15, 2019

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.

AuthZ

It was found that Keycloak's account console, up to 6.0.1, did not perform adequate header checks in some requests

CVE-2019-10199 8.8 - High - August 14, 2019

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.

Improper Input Validation

It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures

CVE-2019-10201 8.1 - High - August 14, 2019

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.

authentification

It was found that Keycloak's Node.js adapter before version 4.8.3 did not properly verify the web token received

CVE-2019-10157 5.5 - Medium - June 12, 2019

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.

authentification

A vulnerability was found in keycloak before 6.0.2

CVE-2019-3875 4.8 - Medium - June 12, 2019

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.

Improper Certificate Validation

Keycloak up to version 6.0.0

CVE-2019-3868 3.8 - Low - April 24, 2019

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 users browser session.

Information Disclosure

The SAML broker consumer endpoint in Keycloak before version 4.6.0.Final ignores expiration conditions on SAML assertions

CVE-2018-14637 8.1 - High - November 30, 2018

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.

authentification

A flaw was found in JBOSS Keycloak 3.2.1.Final

CVE-2018-14658 6.1 - Medium - November 13, 2018

A flaw was found in JBOSS Keycloak 3.2.1.Final. The Redirect URL for both Login and Logout are not normalized in org.keycloak.protocol.oidc.utils.RedirectUtils before the redirect url is verified. This can lead to an Open Redirection attack

Open Redirect

A flaw was found in Keycloak 4.2.1.Final, 4.3.0.Final

CVE-2018-14657 8.1 - High - November 13, 2018

A flaw was found in Keycloak 4.2.1.Final, 4.3.0.Final. When TOPT enabled, an improper implementation of the Brute Force detection algorithm will not enforce its protection measures.

Improper Restriction of Excessive Authentication Attempts

A flaw was found in Keycloak 3.4.3.Final, 4.0.0.Beta2, 4.3.0.Final

CVE-2018-14655 5.4 - Medium - November 13, 2018

A flaw was found in Keycloak 3.4.3.Final, 4.0.0.Beta2, 4.3.0.Final. When using 'response_mode=form_post' it is possible to inject arbitrary Javascript-Code via the 'state'-parameter in the authentication URL. This allows an XSS-Attack upon succesfully login.

XSS

It was found that SAML authentication in Keycloak 3.4.3.Final incorrectly authenticated expired certificates

CVE-2018-10894 5.4 - Medium - August 01, 2018

It was found that SAML authentication in Keycloak 3.4.3.Final incorrectly authenticated expired certificates. A malicious user could use this to access unauthorized data or possibly conduct further attacks.

Improper Certificate Validation

keycloak before version 4.0.0.final is vulnerable to a infinite loop in session replacement

CVE-2018-10912 4.9 - Medium - July 23, 2018

keycloak before version 4.0.0.final is vulnerable to a infinite loop in session replacement. A Keycloak cluster with multiple nodes could mishandle an expired session replacement and lead to an infinite loop. A malicious authenticated user could use this flaw to achieve Denial of Service on the server.

Infinite Loop

It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh token pair

CVE-2017-12160 7.2 - High - October 26, 2017

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.

authentification

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Red Hat Keycloak or by Red Hat? Click the Watch button to subscribe.

Red Hat
Vendor

subscribe