dbcve.org
KeycloakApplication · Redhat

CVE-2024-1722

MEDIUM · 5.3 CVSS v3.1 Published 2024-02-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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 flaw was found in Keycloak. In certain conditions, this issue may allow a remote unauthenticated attacker to block other accounts from logging in.

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

This is a denial of service vulnerability in Keycloak where an unauthenticated remote attacker can exploit certain conditions to prevent legitimate users from logging into their accounts, effectively blocking authentication services.

MitigationRestrict network access to Keycloak servers from untrusted sources and monitor for unusual authentication failures; apply vendor patches or updates when released for this vulnerability.

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:= 23.0.5

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
None
Integrity
None
Availability
Low

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

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 Keycloak server version
    Run 'kc.sh --version' (Keycloak) or check the server startup logs for the version number
    Affected if The installed version is exactly 23.0.5
  2. Verify Keycloak server is reachable over network
    Check network configuration and firewall rules to determine if the Keycloak auth-server endpoints are exposed to untrusted network segments
    Affected if The server is accessible from untrusted network sources without proper access controls
  3. Review authentication endpoint exposure
    Inspect Keycloak configuration files (standalone.xml, cluster-config, or the KEYCLOAK_ADMIN environment settings) to confirm public-facing authentication endpoints
    Affected if Authentication endpoints are exposed to the internet or untrusted networks without IP allowlisting or VPN isolation
  4. Monitor for authentication failures
    Check Keycloak server logs for unusual patterns of failed login attempts or service unavailability, typically found in server.log or audit logs
    Affected if There is a spike in authentication failures or service disruption that correlates with external unauthenticated requests

A user is affected if their Keycloak installation is version 23.0.5 and the authentication endpoints are exposed to untrusted network sources.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to Keycloak servers from untrusted sources and monitor for unusual authentication failures; apply vendor patches or updates when released for this vulnerability.

Recommended fix Moderate confidence

Keycloak 23.0.6 or later (or the latest 23.x stable release)

  1. 1. Identify the current Keycloak version in use (confirm it is 23.0.5)
  2. 2. Check Red Hat advisory RHSA-2024:* or the Keycloak release notes for CVE-2024-1722 to confirm the fixed version
  3. 3. Plan the upgrade, ensuring to backup Keycloak database and configuration before proceeding
  4. 4. Upgrade Keycloak to the fixed version (likely 23.0.6 or later)
  5. 5. After upgrade, verify that authentication works normally and the account lockout behavior is functioning correctly
  6. 6. Test that legitimate users can log in without being blocked by unauthenticated attackers
Caveat Review release notes for any breaking changes between 23.0.5 and the target version; minor version upgrades in Keycloak typically have low risk but always test in staging first

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

Fix this in Keycloak Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1722 — 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-1722 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