dbcve.org
KeycloakApplication · Redhat

CVE-2024-4629

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-03
Fix available
A fix is available. Upgrade to 7.6.10 / 22.012 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Keycloak's brute force protection has a race condition where simultaneous login requests are not properly tracked against failure limits before the lockout threshold is evaluated. Attackers can exploit this timing window by launching parallel login attempts to exceed the configured failed attempt threshold before the system can lock them out.

MitigationApply the vendor patch when available; in the interim, implement additional authentication controls such as network-level rate limiting or multi-factor authentication to supplement Keycloak's built-in brute force protection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KeycloakApplication
Affected:< 24.0.3
Build Of KeycloakApplication
Affected:>= 22.0, < 22.012
Single Sign OnApplication
Affected:all versions>= 7.6, < 7.6.10
Openshift Container PlatformApplication
Affected:= 4.11= 4.12
Openshift Container Platform For LinuxoneApplication
Affected:= 4.9= 4.10
Openshift Container Platform For PowerApplication
Affected:= 4.9= 4.10
Openshift Container Platform Ibm Z SystemsApplication
Affected:= 4.9= 4.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Keycloak version
    Access the Keycloak admin console and navigate to the Server Info section, or check the server startup logs for the version number. Alternatively, query the /health/ready endpoint if exposed.
    Affected if The installed version falls outside the patched ranges: Keycloak < 24.0.3, Keycloak Build >= 22.0 but < 22.012, or RH-SSO >= 7.6 but < 7.6.10 are vulnerable.
  2. Confirm brute force protection is enabled
    In the Keycloak admin console, navigate to Realm Settings > Security Defenses > Brute Force Detection. Verify that the 'Enabled' toggle is turned on.
    Affected if Brute force protection must be enabled for the race condition to be exploitable; if disabled, this specific flaw does not apply.
  3. Review failure threshold and lockout configuration
    In the same Brute Force Detection settings, note the values for 'Max Login Failures' and 'Wait Increment' or 'Lockout Duration'. These determine how many failures trigger lockout.
    Affected if Any non-zero failure threshold represents potential exposure; the race condition allows attackers to exceed this threshold within the timing window before lockout evaluation.
  4. Check OpenShift container platform version if applicable
    If Keycloak is deployed via RH-OCP, run 'oc get clusterversion' to determine the OCP version. For Linuxone, Power, or IBM Z systems, verify the specific build version.
    Affected if OCP versions 4.11, 4.12, 4.9, and 4.10 ship with vulnerable Keycloak versions and are affected.

You are affected if your Keycloak version is below the patched releases AND brute force protection is enabled, allowing attackers to bypass lockout via parallel login attempts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.6.10 / 22.012 / 24.0.3 or later
Fixed in 7.6.1022.01224.0.3
Interim mitigation

Apply the vendor patch when available; in the interim, implement additional authentication controls such as network-level rate limiting or multi-factor authentication to supplement Keycloak's built-in brute force protection.

Recommended fix High confidence

Keycloak 24.0.3 (or 22.0.12 for 22.x builds); RHSSO 7.6.10

  1. Upgrade Keycloak to version 24.0.3 or later to remediate the vulnerability
  2. If running Keycloak build 22.x (versions 22.0 through 22.0.11), upgrade to version 22.0.12 or later
  3. For Red Hat Single Sign On (RHSSO) versions 7.6.x, upgrade to version 7.6.10 or later
  4. For OpenShift Container Platform deployments using the embedded Keycloak operator, apply the corresponding OCP update that includes the fixed Keycloak version (4.11 should upgrade to a version containing Keycloak 22.0.12+, 4.12 should upgrade to a version containing Keycloak 24.0.3+)
  5. After upgrading, verify that brute force protection is functioning correctly by testing with multiple simultaneous login attempts to confirm the lockout mechanism works as expected
Caveat Review Keycloak 24.0.x release notes for any breaking changes or migration requirements before upgrading from earlier versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Keycloak Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4629 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-4629 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data