CVE-2024-1722VulnerabilityPublished 27 Feb 2024Updated 21 Nov 2025

CVE-2024-1722: keycloak · Overly Restrictive Account Lockout Mechanism

Affects keycloakSource CVE Database V5

Not known to be exploited · CVSS 3.7 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

3.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavenorg.keycloak/keycloak`pkg:maven/org.keycloak/keycloak`Other threats	Affected =4.15.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-1722, organizations should first verify if they are running Keycloak version 4.15.0 and plan to upgrade to a patched version once available. In the absence of an official patch, administrators can consider temporarily adjusting account lockout thresholds to reduce the risk of lockout abuse, such as increasing the number of allowed failed login attempts or extending lockout reset intervals. Implementing additional rate limiting and anomaly detection on authentication endpoints can help identify and block suspicious login attempts from remote sources. Monitoring logs for repeated failed login attempts and lockout events is critical to detect potential exploitation attempts early. Employing multi-factor authentication (MFA) can reduce the impact of account lockouts by providing alternative verification methods. Network-level protections such as IP reputation filtering and web application firewalls (WAFs) can also help mitigate automated attack attempts. Finally, maintain close communication with Keycloak vendors and security advisories to apply patches promptly once released.

Description

A flaw was found in Keycloak. In certain conditions, this issue may allow a remote unauthenticated attacker to block other accounts from logging in.

Impact

The primary impact of CVE-2024-1722 is denial of service at the user account level. Attackers can remotely cause legitimate user accounts to become locked out, disrupting access to services protected by Keycloak. This can affect business continuity, user productivity, and customer experience, especially in environments where Keycloak is used for critical authentication. However, since the vulnerability does not allow unauthorized access or data compromise, the confidentiality and integrity of systems remain intact. The scope is limited to environments running the vulnerable Keycloak version (4.15.0). Organizations with high user concurrency or those relying heavily on Keycloak for identity management may experience operational disruptions. The lack of known exploits reduces immediate risk, but the potential for targeted denial-of-service attacks remains a concern. This vulnerability could be leveraged in multi-stage attacks to cause service interruptions or as a nuisance vector in larger campaigns.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 08:46 UTC

Technical details

References

Community reviews

Related threats