Medium Keycloak CVEs
142 CVEs, 2 exploited, 3 protected by Waratek
Overview 142 matches · 3 protected · 2 exploited · 0 CISA KEV · 5 public PoC · 1 EPSS ≥ 0.5
Protected by Waratek
3
2.1%
Rule in development
0
0.0%
Mitigation candidate
5
3.5%
No exploit published
134
94.4%
blocked by ARMR today
3
2.1%
partly blocked
0
0.0%
not blocked
139
97.9%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 67 / year
20171
No exploit published1
Medium1
not blocked1
No public exploit1
20188
No exploit published8
Medium8
not blocked8
No public exploit8
20194
No exploit published4
Medium4
not blocked4
No public exploit4
202014
Mitigation candidate1
No exploit published13
Medium14
not blocked14
Exploited1
No public exploit13
20215
Mitigation candidate1
No exploit published4
Medium5
not blocked5
Working exploit published1
No public exploit4
20227
Protected by Waratek1
Mitigation candidate1
No exploit published5
Medium7
blocked by ARMR today1
not blocked6
Working exploit published1
No public exploit6
20238
Mitigation candidate1
No exploit published7
Medium8
not blocked8
Proof of concept only1
No public exploit7
202413
Mitigation candidate1
No exploit published12
Medium13
not blocked13
Exploited1
No public exploit12
202515
Protected by Waratek1
No exploit published14
Medium15
blocked by ARMR today1
not blocked14
No public exploit15
202667
Protected by Waratek1
No exploit published66
Medium67
blocked by ARMR today1
not blocked66
No public exploit67
2017201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2023-1664 | Medium | 2023-05-26 | No exploit published | No public exploit | 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. |
| CVE-2022-1274 | Medium | 2023-03-29 | No exploit published | No public exploit | 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. |
| CVE-2023-0105 | Medium | 2023-01-13 | No exploit published | No public exploit | A flaw was found in Keycloak. This flaw allows impersonation and lockout due to the email trust not being handled correctly in Keycloak. An attacker can shadow other users with the same email and lockout or impersonate them. |
| CVE-2022-0225 | Medium | 2022-08-26 | No exploit published | No public exploit | 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. |
| CVE-2021-3856 | Medium | 2022-08-26 | Protected by Waratek | No public exploit | 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. |
| CVE-2021-3754 | Medium | 2022-08-26 | No exploit published | No public exploit | 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. |
| CVE-2021-3827 | Medium | 2022-08-23 | No exploit published | No public exploit | 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. |
| CVE-2020-35509 | Medium | 2022-08-23 | No exploit published | No public exploit | 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. |
| CVE-2022-1466 | Medium | 2022-04-26 | No exploit published | No public exploit | 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. |
| CVE-2021-20323 | Medium | 2022-03-25 | Mitigation candidate | Working exploit published | A POST based reflected Cross Site Scripting vulnerability on has been identified in Keycloak. |
| CVE-2021-3424 | Medium | 2021-06-01 | No exploit published | No public exploit | A flaw was found in keycloak as shipped in Red Hat Single Sign-On 7.4 where IDN homograph attacks are possible. A malicious user can register himself with a name already registered and trick admin to grant him extra privileges. |
| CVE-2020-27826 | Medium | 2021-05-28 | No exploit published | No public exploit | 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. |
| CVE-2021-20262 | Medium | 2021-03-09 | No exploit published | No public exploit | 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 user’s browser. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability. |
| CVE-2020-27838 | Medium | 2021-03-08 | Mitigation candidate | Working exploit published | 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. |
| CVE-2020-1725 | Medium | 2021-01-28 | No exploit published | No public exploit | 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. |
| CVE-2020-14302 | Medium | 2020-12-15 | No exploit published | No public exploit | 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. |
| CVE-2020-10770 | Medium | 2020-12-15 | Mitigation candidate | Exploited | 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. |
| CVE-2020-10776 | Medium | 2020-11-17 | No exploit published | No public exploit | 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. |
| CVE-2020-1694 | Medium | 2020-09-16 | No exploit published | No public exploit | 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. |
| CVE-2020-10748 | Medium | 2020-09-16 | No exploit published | No public exploit | A flaw was found in Keycloak's data filter, in version 10.0.1, where it allowed the processing of data URLs in some circumstances. This flaw allows an attacker to conduct cross-site scripting or further attacks. |
| CVE-2020-1727 | Medium | 2020-06-22 | No exploit published | No public exploit | 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. |
| CVE-2020-1758 | Medium | 2020-05-15 | No exploit published | No public exploit | 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. |
| CVE-2020-1724 | Medium | 2020-05-11 | No exploit published | No public exploit | 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. |
| CVE-2020-1698 | Medium | 2020-05-11 | No exploit published | No public exploit | 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. |
| CVE-2020-10686 | Medium | 2020-05-04 | No exploit published | No public exploit | 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. |
| CVE-2020-1728 | Medium | 2020-04-06 | No exploit published | No public exploit | 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. |
| CVE-2020-1744 | Medium | 2020-03-24 | No exploit published | No public exploit | 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. |
| CVE-2020-1697 | Medium | 2020-02-10 | No exploit published | No public exploit | 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. |
| CVE-2019-14820 | Medium | 2020-01-08 | No exploit published | No public exploit | 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. |
| CVE-2014-3652 | Medium | 2019-12-15 | No exploit published | No public exploit | JBoss KeyCloak: Open redirect vulnerability via failure to validate the redirect URL. |
| CVE-2014-3656 | Medium | 2019-12-10 | No exploit published | No public exploit | JBoss KeyCloak: XSS in login-status-iframe.html |
| CVE-2014-3655 | Medium | 2019-11-13 | No exploit published | No public exploit | JBoss KeyCloak is vulnerable to soft token deletion via CSRF |
| CVE-2019-3875 | Medium | 2019-06-12 | No exploit published | No public exploit | 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. |
| CVE-2018-14658 | Medium | 2018-11-13 | No exploit published | No public exploit | 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 |
| CVE-2018-14655 | Medium | 2018-11-13 | No exploit published | No public exploit | 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. |
| CVE-2018-10894 | Medium | 2018-08-01 | No exploit published | No public exploit | 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. |
| CVE-2017-2582 | Medium | 2018-07-26 | No exploit published | No public exploit | 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. |
| CVE-2018-10912 | Medium | 2018-07-23 | No exploit published | No public exploit | 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. |
| CVE-2016-8627 | Medium | 2018-05-11 | No exploit published | No public exploit | admin-cli before versions 3.0.0.alpha25, 2.2.1.cr2 is vulnerable to an EAP feature to download server log files that allows logs to be available via GET requests making them vulnerable to cross-origin attacks. An attacker could trigger the user's browser to request the log files consuming enough resources that normal server functioning could be impaired. |
| CVE-2017-2585 | Medium | 2018-03-12 | No exploit published | No public exploit | 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-2016-8629 | Medium | 2018-03-12 | No exploit published | No public exploit | 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-12158 | Medium | 2017-10-26 | No exploit published | No public exploit | 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. |