Overview 203 matches · 6 protected · 2 exploited · 0 CISA KEV · 8 public PoC · 1 EPSS ≥ 0.5
Protected by Waratek
6
3.0%
Rule in development
0
0.0%
Mitigation candidate
8
3.9%
No exploit published
189
93.1%
blocked by ARMR today
6
3.0%
partly blocked
0
0.0%
not blocked
197
97.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 63 / 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
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
202523
Protected by Waratek1
No exploit published22
High3
Medium16
Low4
blocked by ARMR today1
not blocked22
No public exploit23
202663
Mitigation candidate1
No exploit published62
Critical1
High20
Medium31
Low11
not blocked63
Proof of concept only4
No public exploit59
2017201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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. |