# CVE-2024-4629: Keycloak: potential bypass of brute force protection > Attackers can bypass brute force protection by timing simultaneous login requests, allowing excessive password guessing and potential account compromise. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 3 Sep 2024 - **Updated:** 26 Mar 2026 - **Also known as:** BIT-keycloak-2024-4629, GHSA-gc7q-jgjv-vjr2 ## What is CVE-2024-4629? CVE-2024-4629 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 3 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability was found in Keycloak. This flaw allows attackers to bypass brute force protection by exploiting the timing of login attempts. By initiating multiple login requests simultaneously, attackers can exceed the configured limits for failed attempts before the system locks them out. This timing loophole enables attackers to make more guesses at passwords than intended, potentially compromising account security on affected systems. Weakness: CWE-837 (Improper Enforcement of a Single, Unique Action) ## Which versions are affected by CVE-2024-4629? 7 open source packages ship an affected version, including org.keycloak:keycloak-services and keycloak. It affects 7 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.keycloak:keycloak-services` | Maven | All versions | 22.0.12 | | `org.keycloak:keycloak-services` | Maven | All versions | 22.0.12 | | `org.keycloak:keycloak-services` | Maven | From 23.0.0 | 24.0.7 | | `org.keycloak:keycloak-services` | Maven | From 23.0.0 | 24.0.7 | | `org.keycloak:keycloak-services` | Maven | From 25.0.0 | 25.0.4 | | `org.keycloak:keycloak-services` | Maven | From 25.0.0 | 25.0.4 | | `keycloak` | Bitnami | From 22.0.0 | 22.12.0 | Products: Redhat Build of Keycloak, Redhat Keycloak, Redhat Openshift Container Platform, Redhat Openshift Container Platform for Linuxone, Redhat Openshift Container Platform for Power, Redhat Openshift Container Platform Ibm Z Systems, Redhat Single Sign-On. ## How do I fix CVE-2024-4629? Upgrade org.keycloak:keycloak-services to a fixed version for your release line: 22.0.12, 24.0.7 or 25.0.4. ## Is CVE-2024-4629 being exploited? There is no known exploitation of CVE-2024-4629 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Build of Keycloak - [CVE-2026-15572](https://insights.sbomify.com/CVE-2026-15572/): Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation (high 8.8) - [CVE-2026-3047](https://insights.sbomify.com/CVE-2026-3047/): Keycloak SAML Broken has Authentication Bypass by Primary Weakness (high 8.8) - [CVE-2026-15573](https://insights.sbomify.com/CVE-2026-15573/): Keycloak-services: keycloak-services: authorization bypass via unnormalized uri matching in pathmatcher (high 8.1) - [CVE-2026-16102](https://insights.sbomify.com/CVE-2026-16102/): Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers (high 8.1) - [CVE-2026-1609](https://insights.sbomify.com/CVE-2026-1609/): Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users (high 8.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-4629 and fix it if it is affected. What it is: CVE-2024-4629 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 3 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-4629 in the wild and no public exploit code. Affected packages and fixed versions: - org.keycloak:keycloak-services (Maven): affected all versions; fixed in 22.0.12 - org.keycloak:keycloak-services (Maven): affected all versions; fixed in 22.0.12 - org.keycloak:keycloak-services (Maven): affected from 23.0.0; fixed in 24.0.7 - org.keycloak:keycloak-services (Maven): affected from 23.0.0; fixed in 24.0.7 - org.keycloak:keycloak-services (Maven): affected from 25.0.0; fixed in 25.0.4 - org.keycloak:keycloak-services (Maven): affected from 25.0.0; fixed in 25.0.4 - keycloak (Bitnami): affected from 22.0.0; fixed in 22.12.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-4629/ (Markdown: https://insights.sbomify.com/CVE-2024-4629/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-4629 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-4629 - OSV: https://osv.dev/vulnerability/CVE-2024-4629 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-4629/ Summaries are generated and may contain mistakes; the official description above is the record.