Overview 10 matches · 0 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
10matches
0protected0.0%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
10
100.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
10
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
10
100.0%
split by
peak 4 / month
Apr 191
No exploit published1
Low1
not blocked1
No public exploit1
May 190
Jun 191
No exploit published1
Medium1
not blocked1
No public exploit1
Jul 190
Aug 192
No exploit published2
High2
not blocked2
No public exploit2
Sep 190
Oct 191
No exploit published1
High1
not blocked1
No public exploit1
Nov 191
No exploit published1
Medium1
not blocked1
No public exploit1
Dec 194
No exploit published4
Critical1
High1
Medium2
not blocked4
No public exploit4
Apr 19May 19Jun 19Jul 19Aug 19Sep 19Oct 19Nov 19Dec 19
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2014-3652 | Medium | 2019-12-15 | No exploit published | No public exploit | JBoss KeyCloak: Open redirect vulnerability via failure to validate the redirect URL. |
| CVE-2014-3656 | Medium | 2019-12-10 | No exploit published | No public exploit | JBoss KeyCloak: XSS in login-status-iframe.html |
| CVE-2019-14910 | Critical | 2019-12-05 | No exploit published | No public exploit | A vulnerability was found in keycloak 7.x, when keycloak is configured with LDAP user federation and StartTLS is used instead of SSL/TLS from the LDAP server (ldaps), in this case user authentication succeeds even if invalid password has entered. |
| CVE-2019-14909 | High | 2019-12-04 | No exploit published | No public exploit | A vulnerability was found in Keycloak 7.x where the user federation LDAP bind type is none (LDAP anonymous bind), any password, invalid or valid will be accepted. |
| CVE-2014-3655 | Medium | 2019-11-13 | No exploit published | No public exploit | JBoss KeyCloak is vulnerable to soft token deletion via CSRF |
| CVE-2019-14832 | High | 2019-10-15 | No exploit published | No public exploit | A flaw was found in the Keycloak REST API before version 8.0.0 where it would permit user access from a realm the user was not configured. An authenticated attacker with knowledge of a user id could use this flaw to access unauthorized information or to carry out further attacks. |
| CVE-2019-10201 | High | 2019-08-14 | No exploit published | No public exploit | It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures. If an attacker modifies the SAML Response and removes the <Signature> sections, the message is still accepted, and the message can be modified. An attacker could use this flaw to impersonate other users and gain access to sensitive information. |
| CVE-2019-10199 | High | 2019-08-14 | No exploit published | No public exploit | It was found that Keycloak's account console, up to 6.0.1, did not perform adequate header checks in some requests. An attacker could use this flaw to trick an authenticated user into performing operations via request from an untrusted domain. |
| CVE-2019-3875 | Medium | 2019-06-12 | No exploit published | No public exploit | A vulnerability was found in keycloak before 6.0.2. The X.509 authenticator supports the verification of client certificates through the CRL, where the CRL list can be obtained from the URL provided in the certificate itself (CDP) or through the separately configured path. The CRL are often available over the network through unsecured protocols ('http' or 'ldap') and hence the caller should verify the signature and possibly the certification path. Keycloak currently doesn't validate signatures on CRL, which can result in a possibility of various attacks like man-in-the-middle. |
| CVE-2019-3868 | Low | 2019-04-24 | No exploit published | No public exploit | Keycloak up to version 6.0.0 allows the end user token (access or id token JWT) to be used as the session cookie for browser sessions for OIDC. As a result an attacker with access to service provider backend could hijack user’s browser session. |