Overly Restrictive Account Lockout Mechanism The advisory has been revoked - it doesn't affect any version of package org.keycloak:keycloak-core (opens in a new tab)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGKEYCLOAK-6282945
- published29 Feb 2024
- disclosed21 Feb 2024
- creditUnknown
Introduced: 21 Feb 2024
CVE-2024-1722 (opens in a new tab)How to fix?
Upgrade org.keycloak:keycloak-core to version 24.0.0 or higher.
Amendment
This was deemed not a vulnerability.
Overview
org.keycloak:keycloak-core is an open source identity and access management solution.
Affected versions of this package are vulnerable to Overly Restrictive Account Lockout Mechanism due to a flaw in the account lockout mechanism. This issue may allow a remote unauthenticated attacker to prevent legitimate users from accessing their accounts by exploiting the account lockout functionality.
Note:
This is only exploitable if the realm is configured to use "User (Self) registration", the user registers with a username in email format, and the attacker discovers a valid email address for an account.
Workaround
This vulnerability can be mitigated by putting limits on the frequency of account registration to restrict how often an attacker could utilize this attack and by restricting new account registration to not allow email addresses in the username field, for example, by not allowing the @ symbol. This cannot prevent attacks against existing users who have registered with an email address.