Overview 109 matches · 5 protected · 2 exploited · 0 CISA KEV · 6 public PoC · 1 EPSS ≥ 0.5
Protected by Waratek
5
4.6%
Rule in development
0
0.0%
Mitigation candidate
6
5.5%
No exploit published
98
89.9%
blocked by ARMR today
5
4.6%
partly blocked
0
0.0%
not blocked
104
95.4%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 22 / year
20175
No exploit published5
High4
Medium1
not blocked5
No public exploit5
201812
No exploit published12
High5
Medium7
not blocked12
No public exploit12
201910
No exploit published10
Critical1
High4
Medium4
Low1
not blocked10
No public exploit10
202022
Protected by Waratek2
Mitigation candidate1
No exploit published19
Critical1
High7
Medium14
blocked by ARMR today2
not blocked20
Exploited1
No public exploit21
202111
Mitigation candidate1
No exploit published10
Critical1
High3
Medium5
Low2
not blocked11
Working exploit published1
No public exploit10
202212
Mitigation candidate1
No exploit published11
Critical1
High5
Medium5
Low1
not blocked12
Working exploit published1
No public exploit11
202318
Protected by Waratek2
Mitigation candidate1
No exploit published15
Critical3
High5
Medium9
Low1
blocked by ARMR today2
not blocked16
Proof of concept only1
No public exploit17
202419
Protected by Waratek1
Mitigation candidate2
No exploit published16
High9
Medium9
Low1
blocked by ARMR today1
not blocked18
Exploited1
Working exploit published1
Proof of concept only1
No public exploit16
20172018201920202021202220232024
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-12161 | High | 2018-02-21 | No exploit published | No public exploit | It was found that keycloak before 3.4.2 final would permit misuse of a client-side /etc/hosts entry to spoof a URL in a password reset request. An attacker could use this flaw to craft a malicious password reset request and gain a valid reset token, leading to information disclosure or further attacks. |
| CVE-2014-3651 | High | 2017-12-29 | No exploit published | No public exploit | JBoss KeyCloak before 1.0.3.Final allows remote attackers to cause a denial of service (resource consumption) via a large value in the size parameter to auth/qrcode, related to QR code generation. |
| CVE-2017-12160 | High | 2017-10-26 | No exploit published | No public exploit | 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. |
| CVE-2017-12159 | High | 2017-10-26 | No exploit published | No public exploit | It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session. An attacker could use this flaw to gain access to an authenticated user session, leading to possible information disclosure or further attacks. |
| 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. |
| CVE-2014-3709 | High | 2017-10-18 | No exploit published | No public exploit | The org.keycloak.services.resources.SocialResource.callback method in JBoss KeyCloak before 1.0.3.Final allows remote attackers to conduct cross-site request forgery (CSRF) attacks by leveraging lack of CSRF protection. |