Red Hat Keycloak
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Red Hat Keycloak.
Recent Red Hat Keycloak Security Advisories
Advisory | Title | Published |
---|---|---|
RHSA-2025:0300 | (RHSA-2025:0300) Moderate: Red Hat build of Keycloak 26.0.8 Update | January 13, 2025 |
RHSA-2025:0299 | (RHSA-2025:0299) Moderate: Red Hat build of Keycloak 26.0.8 Images Update | January 13, 2025 |
RHSA-2024:10178 | (RHSA-2024:10178) Important: Red Hat build of Keycloak 26.0.6 Update | November 21, 2024 |
RHSA-2024:10177 | (RHSA-2024:10177) Important: Red Hat build of Keycloak 26.0.6 Images Update | November 21, 2024 |
RHSA-2024:10176 | (RHSA-2024:10176) Important: Red Hat build of Keycloak 24.0.9 Update | November 21, 2024 |
RHSA-2024:10175 | (RHSA-2024:10175) Important: Red Hat build of Keycloak 24.0.9 Images Update | November 21, 2024 |
RHSA-2024:6890 | (RHSA-2024:6890) Important: Red Hat build of Keycloak 24.0.8 Update | September 19, 2024 |
RHSA-2024:6889 | (RHSA-2024:6889) Important: Red Hat build of Keycloak 24.0.8 Images Update | September 19, 2024 |
RHSA-2024:6888 | (RHSA-2024:6888) Important: Red Hat build of Keycloak 22.0.13 Update | September 19, 2024 |
RHSA-2024:6887 | (RHSA-2024:6887) Important: Red Hat build of Keycloak 22.0.13 Images Update | September 19, 2024 |
By the Year
In 2025 there have been 0 vulnerabilities in Red Hat Keycloak. Last year, in 2024 Keycloak had 12 security vulnerabilities published. Right now, Keycloak is on track to have less security vulnerabilities in 2025 than it did last year.
Year | Vulnerabilities | Average Score |
---|---|---|
2025 | 0 | 0.00 |
2024 | 12 | 6.18 |
2023 | 13 | 6.44 |
2022 | 14 | 6.75 |
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
Keycloak: Sensitive Information Disclosure in JGroups Replication Configuration
CVE-2024-10973
5.7 - Medium
- December 17, 2024
A vulnerability was found in Keycloak. The environment option `KC_CACHE_EMBEDDED_MTLS_ENABLED` does not work and the JGroups replication configuration is always used in plain text which can allow an attacker that has access to adjacent networks related to JGroups to read sensitive information.
Cleartext Transmission of Sensitive Information
Keycloak Server: Denial of Service via Improper Proxy Header Validation
CVE-2024-9666
4.7 - Medium
- November 25, 2024
A vulnerability was found in the Keycloak Server. The Keycloak Server is vulnerable to a denial of service (DoS) attack due to improper handling of proxy headers. When Keycloak is configured to accept incoming proxy headers, it may accept non-IP values, such as obfuscated identifiers, without proper validation. This issue can lead to costly DNS resolution operations, which an attacker could exploit to tie up IO threads and potentially cause a denial of service. The attacker must have access to send requests to a Keycloak instance that is configured to accept proxy headers, specifically when reverse proxies do not overwrite incoming headers, and Keycloak is configured to trust these headers.
HTTP Request Smuggling
Keycloak-services: Denial of Service via Regex Complexity in SearchQueryUtils
CVE-2024-10270
6.5 - Medium
- November 25, 2024
A vulnerability was found in the Keycloak-services package. If untrusted data is passed to the SearchQueryUtils method, it could lead to a denial of service (DoS) scenario by exhausting system resources due to a Regex complexity.
ReDoS
Keycloak Information Disclosure Vulnerability in Build Process
CVE-2024-10451
5.9 - Medium
- November 25, 2024
A flaw was found in Keycloak. This issue occurs because sensitive runtime values, such as passwords, may be captured during the Keycloak build process and embedded as default values in bytecode, leading to unintended information disclosure. In Keycloak 26, sensitive data specified directly in environment variables during the build process is also stored as a default values, making it accessible during runtime. Indirect usage of environment variables for SPI options and Quarkus properties is also vulnerable due to unconditional expansion by PropertyMapper logic, capturing sensitive data as default values in all Keycloak versions up to 26.0.2.
Use of Hard-coded Credentials
Keycloak Privilege Escalation via Vault File Access
CVE-2024-10492
- November 25, 2024
A vulnerability was found in Keycloak. A user with high privileges could read sensitive information from a Vault file that is not within the expected context. This attacker must have previous high access to the Keycloak server in order to perform resource creation, for example, an LDAP provider configuration and set up a Vault read file, which will only inform whether that file exists or not.
External Control of File Name or Path
Keycloak: Improper Token Type Enforcement in Signature Validation
CVE-2023-0657
3.4 - Low
- November 17, 2024
A flaw was found in Keycloak. This issue occurs due to improperly enforcing token types when validating signatures locally. This could allow an authenticated attacker to exchange a logout token for an access token and possibly gain access to data outside of enforced permissions.
Improper Check for Dropped Privileges
Keycloak LDAP Injection Vulnerability
CVE-2022-2232
7.5 - High
- November 14, 2024
A flaw was found in the Keycloak package. This flaw allows an attacker to utilize an LDAP injection to bypass the username lookup or potentially perform other malicious actions.
Improper Input Validation
A denial of service vulnerability was found in keycloak where the amount of attributes per object is not limited
CVE-2023-6841
7.5 - High
- September 10, 2024
A denial of service vulnerability was found in keycloak where the amount of attributes per object is not limited,an attacker by sending repeated HTTP requests could cause a resource exhaustion when the application send back rows with long attribute values.
Improper Handling of Extra Values
A session fixation issue was discovered in the SAML adapters provided by Keycloak
CVE-2024-7341
7.1 - High
- September 09, 2024
A session fixation issue was discovered in the SAML adapters provided by Keycloak. The session ID and JSESSIONID cookie are not changed at login time, even when the turnOffChangeSessionIdOnLogin option is configured. This flaw allows an attacker who hijacks the current session before authentication to trigger session fixation.
Session Fixation
An open redirect vulnerability was found in Keycloak
CVE-2024-7260
6.1 - Medium
- September 09, 2024
An open redirect vulnerability was found in Keycloak. A specially crafted URL can be constructed where the referrer and referrer_uri parameters are made to trick a user to visit a malicious webpage. A trusted URL can trick users and automation into believing that the URL is safe, when, in fact, it redirects to a malicious server. This issue can result in a victim inadvertently trusting the destination of the redirect, potentially leading to a successful phishing attack or other types of attacks. Once a crafted URL is made, it can be sent to a Keycloak admin via email for example. This will trigger this vulnerability when the user visits the page and clicks the link. A malicious actor can use this to target users they know are Keycloak admins for further attacks. It may also be possible to bypass other domain-related security checks, such as supplying this as a OAuth redirect uri. The malicious actor can further obfuscate the redirect_uri using URL encoding, to hide the text of the actual malicious website domain.
Open Redirect
A vulnerability was found in Keycloak
CVE-2024-4629
6.5 - Medium
- September 03, 2024
A vulnerability was found in Keycloak. This flaw allows attackers to bypass brute force protection by exploiting the timing of login attempts. By initiating multiple login requests simultaneously, attackers can exceed the configured limits for failed attempts before the system locks them out. This timing loophole enables attackers to make more guesses at passwords than intended, potentially compromising account security on affected systems.
Improper Enforcement of a Single, Unique Action
A flaw was found in the redirect_uri validation logic in Keycloak
CVE-2023-6291
7.1 - High
- January 26, 2024
A flaw was found in the redirect_uri validation logic in Keycloak. This issue may allow a bypass of otherwise explicitly allowed hosts. A successful attack may lead to an access token being stolen, making it possible for the attacker to impersonate other users.
Open Redirect
A flaw was found in Keycloak
CVE-2023-6927
6.1 - Medium
- December 18, 2023
A flaw was found in Keycloak. This issue may allow an attacker to steal authorization codes or tokens from clients using a wildcard in the JARM response mode "form_post.jwt" which could be used to bypass the security patch implemented to address CVE-2023-6134.
Open Redirect
The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such
CVE-2023-48795
5.9 - Medium
- December 18, 2023
The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.
Improper Validation of Integrity Check Value
A flaw was found in Keycloak that prevents certain schemes in redirects, but permits them if a wildcard is appended to the token
CVE-2023-6134
5.4 - Medium
- December 14, 2023
A flaw was found in Keycloak that prevents certain schemes in redirects, but permits them if a wildcard is appended to the token. This issue could allow an attacker to submit a specially crafted request leading to cross-site scripting (XSS) or further attacks. This flaw is the result of an incomplete fix for CVE-2020-10748.
XSS
An unconstrained memory consumption vulnerability was discovered in Keycloak
CVE-2023-6563
7.7 - High
- December 14, 2023
An unconstrained memory consumption vulnerability was discovered in Keycloak. It can be triggered in environments which have millions of offline tokens (> 500,000 users with each having at least 2 saved sessions). If an attacker creates two or more user sessions and then open the "consents" tab of the admin User Interface, the UI attempts to load a huge number of offline client sessions leading to excessive memory and CPU consumption which could potentially crash the entire system.
Allocation of Resources Without Limits or Throttling
A reflected cross-site scripting (XSS) vulnerability was found in the 'oob' OAuth endpoint due to incorrect null-byte handling
CVE-2022-4137
6.1 - Medium
- September 25, 2023
A reflected cross-site scripting (XSS) vulnerability was found in the 'oob' OAuth endpoint due to incorrect null-byte handling. This issue allows a malicious link to insert an arbitrary URI into a Keycloak error page. This flaw requires a user or administrator to interact with a link in order to be vulnerable. This may compromise user details, allowing it to be changed or collected by an attacker.
XSS
A flaw was found in the offline_access scope in Keycloak
CVE-2022-3916
6.8 - Medium
- September 20, 2023
A flaw was found in the offline_access scope in Keycloak. This issue would affect users of shared computers more (especially if cookies are not cleared), due to a lack of root session validation, and the reuse of session ids across root and user authentication sessions. This enables an attacker to resolve a user session attached to a previously authenticated user; when utilizing the refresh token, they will be issued a token for the original user.
Insufficient Session Expiration
A flaw was found in Keycloak
CVE-2022-1438
4.8 - Medium
- September 20, 2023
A flaw was found in Keycloak. Under specific circumstances, HTML entities are not sanitized during user impersonation, resulting in a Cross-site scripting (XSS) vulnerability.
XSS
A flaw was found in the Keycloak package, more specifically org.keycloak.userprofile
CVE-2023-4918
8.8 - High
- September 12, 2023
A flaw was found in the Keycloak package, more specifically org.keycloak.userprofile. When a user registers itself through registration flow, the "password" and "password-confirm" field from the form will occur as regular user attributes. All users and clients with proper rights and roles are able to read users attributes, allowing a malicious user with minimal access to retrieve the users passwords in clear text, jeopardizing their environment.
Cleartext Transmission of Sensitive Information
A flaw was found in Keycloaks OpenID Connect user authentication, which may incorrectly authenticate requests
CVE-2023-0264
5 - Medium
- August 04, 2023
A flaw was found in Keycloaks OpenID Connect user authentication, which may incorrectly authenticate requests. An authenticated attacker who could obtain information from a user request within the same realm could use that data to impersonate the victim and generate new session tokens. This issue could impact confidentiality, integrity, and availability.
authentification
Keycloak
CVE-2022-4361
6.1 - Medium
- July 07, 2023
Keycloak, an open-source identity and access management solution, has a cross-site scripting (XSS) vulnerability in the SAML or OIDC providers. The vulnerability can allow an attacker to execute malicious scripts by setting the AssertionConsumerServiceURL value or the redirect_uri.
XSS
A flaw was found in Keycloak
CVE-2023-1664
6.5 - Medium
- May 26, 2023
A flaw was found in Keycloak. This flaw depends on a non-default configuration "Revalidate Client Certificate" to be enabled and the reverse proxy is not validating the certificate before Keycloak. Using this method an attacker may choose the certificate which will be validated by the server. If this happens and the KC_SPI_TRUSTSTORE_FILE_FILE variable is missing/misconfigured, any trustfile may be accepted with the logging information of "Cannot validate client certificate trust: Truststore not available". This may not impact availability as the attacker would have no access to the server, but consumer applications Integrity or Confidentiality may be impacted considering a possible access to them. Considering the environment is correctly set to use "Revalidate Client Certificate" this flaw is avoidable.
Improper Certificate Validation
A flaw was found in Keycloak in the execute-actions-email endpoint
CVE-2022-1274
5.4 - Medium
- March 29, 2023
A flaw was found in Keycloak in the execute-actions-email endpoint. This issue allows arbitrary HTML to be injected into emails sent to Keycloak users and can be misused to perform phishing or other attacks against users.
XSS
keycloak: path traversal via double URL encoding
CVE-2022-3782
9.1 - Critical
- January 13, 2023
keycloak: path traversal via double URL encoding. A flaw was found in Keycloak, where it does not properly validate URLs included in a redirect. An attacker can use this flaw to construct a malicious request to bypass validation and access other URLs and potentially sensitive information within the domain or possibly conduct further attacks. This flaw affects any client that utilizes a wildcard in the Valid Redirect URIs field.
Directory traversal
Rejected reason: The originally reported issue in https://github.com/syedsohaibkarim/OpenRedirect-Keycloak18.0.0 is a known misconfiguration
CVE-2022-1970
- October 19, 2022
Rejected reason: The originally reported issue in https://github.com/syedsohaibkarim/OpenRedirect-Keycloak18.0.0 is a known misconfiguration, and recommendation already exists in the Keycloak documentation to mitigate the issue: https://www.keycloak.org/docs/latest/server_admin/index.html#open-redirectors.
A flaw was found in Keycloak
CVE-2022-0225
5.4 - Medium
- August 26, 2022
A flaw was found in Keycloak. This flaw allows a privileged attacker to use the malicious payload as the group name while creating a new group from the admin console, leading to a stored Cross-site scripting (XSS) attack.
XSS
A flaw was found in Keycloak
CVE-2021-3632
7.5 - High
- August 26, 2022
A flaw was found in Keycloak. This vulnerability allows anyone to register a new security device or key when there is not a device already registered for any user by using the WebAuthn password-less login flow.
authentification
A flaw was found in keycloak where an attacker is able to register himself with the username same as the email ID of any existing user
CVE-2021-3754
5.3 - Medium
- August 26, 2022
A flaw was found in keycloak where an attacker is able to register himself with the username same as the email ID of any existing user. This may cause trouble in getting password recovery email in case the user forgets the password.
ClassLoaderTheme and ClasspathThemeResourceProviderFactory allows reading any file available as a resource to the classloader
CVE-2021-3856
4.3 - Medium
- August 26, 2022
ClassLoaderTheme and ClasspathThemeResourceProviderFactory allows reading any file available as a resource to the classloader. By sending requests for theme resources with a relative path from an external HTTP client, the client will receive the content of random files if available.
Directory traversal
A flaw was found in keycloak affecting versions 11.0.3 and 12.0.0
CVE-2020-35509
5.4 - Medium
- August 23, 2022
A flaw was found in keycloak affecting versions 11.0.3 and 12.0.0. An expired certificate would be accepted by the direct-grant authenticator because of missing time stamp validations. The highest threat from this vulnerability is to data confidentiality and integrity.
Improper Certificate Validation
A flaw was found in keycloak, where the default ECP binding flow allows other authentication flows to be bypassed
CVE-2021-3827
6.8 - Medium
- August 23, 2022
A flaw was found in keycloak, where the default ECP binding flow allows other authentication flows to be bypassed. By exploiting this behavior, an attacker can bypass the MFA authentication by sending a SOAP request with an AuthnRequest and Authorization header with the user's credentials. The highest threat from this vulnerability is to confidentiality and integrity.
authentification
A flaw was found in keycloak where a brute force attack is possible even when the permanent lockout feature is enabled
CVE-2021-3513
7.5 - High
- August 22, 2022
A flaw was found in keycloak where a brute force attack is possible even when the permanent lockout feature is enabled. This is due to a wrong error message displayed when wrong credentials are entered. The highest threat from this vulnerability is to confidentiality.
Generation of Error Message Containing Sensitive Information
An issue was discovered in Keycloak
CVE-2022-2668
7.2 - High
- August 05, 2022
An issue was discovered in Keycloak that allows arbitrary Javascript to be uploaded for the SAML protocol mapper even if the UPLOAD_SCRIPTS feature is disabled
A privilege escalation flaw was found in the token exchange feature of keycloak
CVE-2022-1245
9.8 - Critical
- July 08, 2022
A privilege escalation flaw was found in the token exchange feature of keycloak. Missing authorization allows a client application holding a valid access token to exchange tokens for any target client by passing the client_id of the target. This could allow a client to gain unauthorized access to additional services.
Insecure Direct Object Reference / IDOR
Due to improper authorization, Red Hat Single Sign-On is vulnerable to users performing actions that they should not be allowed to perform
CVE-2022-1466
6.5 - Medium
- April 26, 2022
Due to improper authorization, Red Hat Single Sign-On is vulnerable to users performing actions that they should not be allowed to perform. It was possible to add users to the master realm even though no respective permission was granted.
AuthZ
A flaw was found in keycloak where keycloak may fail to logout user session if the logout request comes
CVE-2021-3461
7.1 - High
- April 01, 2022
A flaw was found in keycloak where keycloak may fail to logout user session if the logout request comes from external SAML identity provider and Principal Type is set to Attribute [Name].
Insufficient Session Expiration
A POST based reflected Cross Site Scripting vulnerability on has been identified in Keycloak.
CVE-2021-20323
6.1 - Medium
- March 25, 2022
A POST based reflected Cross Site Scripting vulnerability on has been identified in Keycloak.
XSS
A flaw was found in Keycloak in versions from 12.0.0 and before 15.1.1 which
CVE-2021-4133
8.8 - High
- January 25, 2022
A flaw was found in Keycloak in versions from 12.0.0 and before 15.1.1 which allows an attacker with any existing user account to create new default user accounts via the administrative REST API even when new user registration is disabled.
AuthZ
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 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 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.
Output Sanitization
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.
XSS
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 Gatekeeper, where on using lower case HTTP headers (
CVE-2020-14359
7.3 - High
- February 23, 2021
A vulnerability was found in all versions of Keycloak Gatekeeper, where on using lower case HTTP headers (via cURL) an attacker 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 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 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 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.
SSRF
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.
Use of Password Hash With Insufficient Computational Effort
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
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.
Insertion of Sensitive Information into Log File
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.
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.
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.
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.
Improper Handling of Exceptional Conditions
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.
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.
Session Riding
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
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
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
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 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
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 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
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.