CyberRota Analysis
AI-GeneratedKeycloak deployed in stateless mode with MySQL or MariaDB is vulnerable due to a mismatch in row-count semantics, allowing attackers to bypass replay protection. This flaw enables the interception and replay of single-use security artifacts, such as JWT client assertions and TOTP codes, potentially granting unauthorized access to sensitive token endpoints or login flows. Organizations utilizing Keycloak in this configuration should prioritize addressing this vulnerability to safeguard their authentication processes.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
A flaw was found in Keycloak. When deployed in stateless mode with MySQL or MariaDB, a mismatch in row-count semantics between the database driver and Keycloak's application logic allows an attacker to bypass replay protection. This vulnerability enables an attacker who intercepts single-use security artifacts, such as JWT client assertions, DPoP proofs, or one-time password (TOTP) codes, to replay them. Successful exploitation grants unauthorized access to the token endpoint or login flow.