Keycloak-core: dos via account lockout
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| unaffected |
|
||||||||
| Red Hat | Red Hat Build of Keycloak | affected | — | ||||||
| Red Hat | Red Hat Single Sign-On 7 | affected | — |
No data.
No data available yet.
Vendor Workaround
Red Hat Product Security is not aware of a way to completely mitigate this issue. However, the following techniques can be used to help prevent exploitation: - Put limits on frequency of account registration, restricting how often an attacker could utilize this attack - Restrict new account registration to not allow email addresses in the username field, for example, by not allowing the "@" symbol. Note: this cannot prevent attacks against existing users who have registered with an email address. If this vulnerability has been triggered, an administrator has two options to remedy it manually by modifying the second account (of the attacker): - Delete the account - Change the username
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-2026 | A flaw was found in Keycloak. In certain conditions, this issue may allow a remote unauthenticated attacker to block other accounts from logging in. |
Github GHSA |
GHSA-cq42-vhv7-xr7p | Keycloak Denial of Service via account lockout |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.771% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat keycloak
|
|
| Weaknesses | NVD-CWE-noinfo | |
| CPEs | cpe:2.3:a:redhat:keycloak:23.0.5:*:*:*:*:*:*:* | |
| Vendors & Products |
Redhat keycloak
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:build_keycloak: |
Overly Restrictive Account Lockout Mechanism