Overview 9 matches · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
9matches
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
9
100.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
9
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
9
100.0%
split by
peak 2 / quarter
Q2 191
No exploit published1
Low1
not blocked1
No public exploit1
Q3 190
Q4 190
Q1 200
Q2 200
Q3 200
Q4 200
Q1 212
No exploit published2
Low2
not blocked2
No public exploit2
Q2 210
Q3 210
Q4 210
Q1 220
Q2 220
Q3 221
No exploit published1
Low1
not blocked1
No public exploit1
Q4 220
Q1 231
No exploit published1
Low1
not blocked1
No public exploit1
Q2 230
Q3 230
Q4 230
Q1 240
Q2 241
No exploit published1
Low1
not blocked1
No public exploit1
Q3 240
Q4 242
No exploit published2
Low2
not blocked2
No public exploit2
Q1 251
No exploit published1
Low1
not blocked1
No public exploit1
Q3 19Q1 20Q3 20Q1 21Q3 21Q1 22Q3 22Q1 23Q3 23Q1 24Q3 24Q1 25
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-4028 | Low | 2025-02-18 | No exploit published | No public exploit | A vulnerability was found in Keycloak. This issue may allow a privileged attacker to use a malicious payload as the permission while creating items (Resource and Permissions) from the admin console, leading to a stored cross-site scripting (XSS) attack. |
| CVE-2024-10492 | Low | 2024-11-25 | No exploit published | No public exploit | 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. |
| CVE-2023-0657 | Low | 2024-11-17 | No exploit published | No public exploit | 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. |
| CVE-2024-5967 | Low | 2024-06-18 | No exploit published | No public exploit | A vulnerability was found in Keycloak. The LDAP testing endpoint allows changing the Connection URL independently without re-entering the currently configured LDAP bind credentials. This flaw allows an attacker with admin access (permission manage-realm) to change the LDAP host URL ("Connection URL") to a machine they control. The Keycloak server will connect to the attacker's host and try to authenticate with the configured credentials, thus leaking them to the attacker. As a consequence, an attacker who has compromised the admin console or compromised a user with sufficient privileges can leak domain credentials and attack the domain. |
| CVE-2023-0091 | Low | 2023-01-13 | No exploit published | No public exploit | A flaw was found in Keycloak, where it did not properly check client tokens for possible revocation in its client credential flow. This flaw allows an attacker to access or modify potentially sensitive information. |
| CVE-2022-2256 | Low | 2022-09-01 | No exploit published | No public exploit | A Stored Cross-site scripting (XSS) vulnerability was found in keycloak as shipped in Red Hat Single Sign-On 7. This flaw allows a privileged attacker to execute malicious scripts in the admin console, abusing the default roles functionality. |
| CVE-2020-1717 | Low | 2021-02-11 | No exploit published | No public exploit | A flaw was found in Keycloak 7.0.1. A logged in user can do an account email enumeration attack. |
| CVE-2020-10734 | Low | 2021-02-11 | No exploit published | No public exploit | 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. |
| CVE-2019-3868 | Low | 2019-04-24 | No exploit published | No public exploit | 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. |