CVE-2024-1722
Redhat Keycloak 23.0.5
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LSummary
CVE-2024-1722 is a low-severity Overly Restrictive Account Lockout Mechanism (CWE-645) vulnerability in Redhat Keycloak. Its CVSS base score is 3.7 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Account Access Removal (T1531); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-7 (Unsuccessful Logon Attempts) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-2026
Vulnerability Data
A flaw was found in Keycloak. In certain conditions, this issue may allow a remote unauthenticated attacker to block other accounts from logging in.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Properly tuned thresholds and lock durations in the unsuccessful logon control stop an overly sensitive lockout from being introduced or exploited for DoS.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Credential management policies directly govern lockout thresholds and reset procedures.
Authentication policies include lockout parameters that must not be overly restrictive.
Authorization policy definition and review encompass account lockout rules and exceptions.
Monitoring can detect resulting lockouts but does not prevent an overly restrictive mechanism.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Access control policy should define lockout thresholds and recovery procedures to avoid overly restrictive denial-of-service.
Authentication information management includes setting lockout parameters that balance security against accidental lockouts.
Access rights administration must include procedures for unlocking accounts and reviewing lockout events.
Secure authentication mechanisms directly specify lockout thresholds, unlock processes, and monitoring to prevent abuse.
Logging of authentication events enables detection of lockout abuse but does not prevent the weakness itself.
Monitoring can detect excessive lockouts but does not define or enforce appropriate lockout parameters.