Overview 6 matches · 0 protected · 2 exploited · 0 CISA KEV · 1 EPSS ≥ 0.5
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
6
100.0%
No exploit published
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
6
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
33.3%
Working exploit published
3
50.0%
Proof of concept only
1
16.7%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 2 / quarter
Q4 201
Mitigation candidate1
Medium1
not blocked1
Exploited1
Q1 211
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
Q2 210
Q3 210
Q4 210
Q1 221
Mitigation candidate1
Medium1
not blocked1
Working exploit published1
Q2 220
Q3 220
Q4 220
Q1 230
Q2 230
Q3 231
Mitigation candidate1
Medium1
not blocked1
Proof of concept only1
Q4 230
Q1 240
Q2 240
Q3 242
Mitigation candidate2
High1
Medium1
not blocked2
Exploited1
Working exploit published1
Q1 21Q3 21Q1 22Q3 22Q1 23Q3 23Q1 24Q3 24
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-8883 | Medium | 2024-09-19 | Mitigation candidate | Exploited | A misconfiguration flaw was found in Keycloak. This issue can allow an attacker to redirect users to an arbitrary URL if a 'Valid Redirect URI' is set to http://localhost or http://127.0.0.1, enabling sensitive information such as authorization codes to be exposed to the attacker, potentially leading to session hijacking. |
| CVE-2024-8698 | High | 2024-09-19 | Mitigation candidate | Working exploit published | A flaw exists in the SAML signature validation method within the Keycloak XMLSignatureUtil class. The method incorrectly determines whether a SAML signature is for the full document or only for specific assertions based on the position of the signature in the XML document, rather than the Reference element used to specify the signed element. This flaw allows attackers to create crafted responses that can bypass the validation, potentially leading to privilege escalation or impersonation attacks. |
| CVE-2023-0264 | Medium | 2023-08-04 | Mitigation candidate | Proof of concept only | 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. |
| 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-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-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. |