High Oak-core CVEs
15 CVEs, 1 protected by Waratek
Overview 15 matches · 1 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
1
6.7%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
14
93.3%
blocked by ARMR today
1
6.7%
partly blocked
0
0.0%
not blocked
14
93.3%
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
15
100.0%
split by
peak 4 / year
20171
No exploit published1
High1
not blocked1
No public exploit1
20184
No exploit published4
High4
not blocked4
No public exploit4
20192
No exploit published2
High2
not blocked2
No public exploit2
20204
Protected by Waratek1
No exploit published3
High4
blocked by ARMR today1
not blocked3
No public exploit4
20211
No exploit published1
High1
not blocked1
No public exploit1
20221
No exploit published1
High1
not blocked1
No public exploit1
20231
No exploit published1
High1
not blocked1
No public exploit1
20241
No exploit published1
High1
not blocked1
No public exploit1
20172018201920202021202220232024
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2023-6841 | High | 2024-09-10 | No exploit published | No public exploit | A denial of service vulnerability was found in keycloak where the amount of attributes per object is not limited,an attacker by sending repeated HTTP requests could cause a resource exhaustion when the application send back rows with long attribute values. |
| CVE-2023-4918 | High | 2023-09-12 | No exploit published | No public exploit | A flaw was found in the Keycloak package, more specifically org.keycloak.userprofile. When a user registers itself through registration flow, the "password" and "password-confirm" field from the form will occur as regular user attributes. All users and clients with proper rights and roles are able to read users attributes, allowing a malicious user with minimal access to retrieve the users passwords in clear text, jeopardizing their environment. |
| CVE-2021-3632 | High | 2022-08-26 | No exploit published | No public exploit | A flaw was found in Keycloak. This vulnerability allows anyone to register a new security device or key when there is not a device already registered for any user by using the WebAuthn password-less login flow. |
| CVE-2021-20202 | High | 2021-05-12 | No exploit published | No public exploit | A flaw was found in keycloak. Directories can be created prior to the Java process creating them in the temporary directory, but with wider user permissions, allowing the attacker to have access to the contents that keycloak stores in this directory. The highest threat from this vulnerability is to data confidentiality and integrity. |
| CVE-2020-14389 | High | 2020-11-17 | No exploit published | No public exploit | It was found that Keycloak before version 12.0.0 would permit a user with only view-profile role to manage the resources in the new account console, allowing access and modification of data the user was not intended to have. |
| CVE-2020-1714 | High | 2020-05-13 | Protected by Waratek | No public exploit | A flaw was found in Keycloak before version 11.0.0, where the code base contains usages of ObjectInputStream without type checks. This flaw allows an attacker to inject arbitrarily serialized Java Objects, which would then get deserialized in a privileged context and potentially lead to remote code execution. |
| CVE-2019-10170 | High | 2020-05-08 | No exploit published | No public exploit | A flaw was found in the Keycloak admin console, where the realm management interface permits a script to be set via the policy. This flaw allows an attacker with authenticated user and realm management permissions to configure a malicious script to trigger and execute arbitrary code with the permissions of the application user. |
| CVE-2020-1940 | High | 2020-01-28 | No exploit published | No public exploit | The optional initial password change and password expiration features present in Apache Jackrabbit Oak 1.2.0 to 1.22.0 are prone to a sensitive information disclosure vulnerability. The code mandates the changed password to be passed as an additional attribute to the credentials object but does not remove it upon processing during the first phase of the authentication. In combination with additional, independent authentication mechanisms, this may lead to the new password being disclosed. |
| 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-2018-14637 | High | 2018-11-30 | No exploit published | No public exploit | The SAML broker consumer endpoint in Keycloak before version 4.6.0.Final ignores expiration conditions on SAML assertions. An attacker can exploit this vulnerability to perform a replay attack. |
| CVE-2016-8609 | High | 2018-08-01 | No exploit published | No public exploit | It was found that the keycloak before 2.3.0 did not implement authentication flow correctly. An attacker could use this flaw to construct a phishing URL, from which he could hijack the user's session. This could lead to information disclosure, or permit further possible attacks. |
| CVE-2017-2646 | High | 2018-07-27 | No exploit published | No public exploit | It was found that when Keycloak before 2.5.5 receives a Logout request with a Extensions in the middle of the request, the SAMLSloRequestParser.parse() method ends in a infinite loop. An attacker could use this flaw to conduct denial of service attacks. |
| 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. |