Medium Org.keycloak CVEs
106 CVEs, 2 exploited, 3 protected by Waratek
Overview 106 matches · 3 protected · 2 exploited · 0 CISA KEV · 5 public PoC · 1 EPSS ≥ 0.5
Protected by Waratek
3
2.8%
Rule in development
0
0.0%
Mitigation candidate
5
4.7%
No exploit published
98
92.5%
blocked by ARMR today
3
2.8%
partly blocked
0
0.0%
not blocked
103
97.2%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 34 / year
20171
No exploit published1
Medium1
not blocked1
No public exploit1
20187
No exploit published7
Medium7
not blocked7
No public exploit7
20194
No exploit published4
Medium4
not blocked4
No public exploit4
202012
Mitigation candidate1
No exploit published11
Medium12
not blocked12
Exploited1
No public exploit11
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
202634
Protected by Waratek1
No exploit published33
Medium34
blocked by ARMR today1
not blocked33
No public exploit34
2017201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-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. |