Overview 208 matches · 206 in Waratek scope · 8 protected · 3 exploited · 0 CISA KEV · 9 public PoC · 1 EPSS ≥ 0.5
208matches
206in Waratek scope99.0%
8protected3.8%
3exploited1.4%
0CISA KEV0.0%
9public PoC4.3%
1EPSS ≥ 0.50.5%
Protected by Waratek
8
3.8%
Rule in development
0
0.0%
Mitigation candidate
9
4.3%
No exploit published
189
90.9%
Outside Waratek scope
0
0.0%
Not applicable
0
0.0%
Withdrawn CVE
2
1.0%
blocked by ARMR today
8
3.8%
partly blocked
0
0.0%
not blocked
200
96.2%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 70 / year
20175
No exploit published5
High4
Medium1
not blocked5
No public exploit5
201813
No exploit published12
Withdrawn CVE1
High5
Medium7
Unknown1
not blocked13
No public exploit13
201910
No exploit published10
Critical1
High4
Medium4
Low1
not blocked10
No public exploit10
202021
Protected by Waratek2
Mitigation candidate1
No exploit published18
Critical2
High7
Medium12
blocked by ARMR today2
not blocked19
Exploited1
No public exploit20
202111
Mitigation candidate1
No exploit published10
Critical1
High3
Medium5
Low2
not blocked11
Working exploit published1
No public exploit10
202214
Protected by Waratek1
Mitigation candidate1
No exploit published12
Critical1
High5
Medium7
Low1
blocked by ARMR today1
not blocked13
Working exploit published1
No public exploit13
202316
Protected by Waratek2
Mitigation candidate1
No exploit published13
Critical2
High5
Medium8
Low1
blocked by ARMR today2
not blocked14
Proof of concept only1
No public exploit15
202427
Protected by Waratek1
Mitigation candidate3
No exploit published23
High11
Medium13
Low3
blocked by ARMR today1
not blocked26
Exploited1
Working exploit published2
Proof of concept only1
No public exploit23
202521
Protected by Waratek1
No exploit published20
High3
Medium15
Low3
blocked by ARMR today1
not blocked20
No public exploit21
202670
Protected by Waratek1
Mitigation candidate2
No exploit published66
Withdrawn CVE1
Critical1
High22
Medium34
Low12
Unknown1
blocked by ARMR today1
not blocked69
Exploited1
Proof of concept only2
No public exploit67
2017201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-2017-1000500 | Unknown | 2018-01-03 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-12161. Reason: This candidate is a reservation duplicate of CVE-2017-12161. Notes: All CVE users should reference CVE-2017-12161 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage |
| 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. |