Skip to content
Fencer Vulns
low 3.7

CVE-2024-1722 json

Keycloak-core: dos via account lockout

published 2024-02-27 2 y ago modified 2026-06-17 4 mo ago also GHSA-cq42-vhv7-xr7p , EUVD-2024-2026

cvss
3.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

A flaw was found in Keycloak. In certain conditions, this issue may allow a remote unauthenticated attacker to block other accounts from logging in.

Patch / fix

  • maven org.keycloak:keycloak-services 24.0.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-1722 updated cvss 3.7

keycloak-core: DoS via account lockout

  • Red Hat Build of Keycloak keycloak-core
    affected: workaround, no fix available
  • Red Hat Single Sign-On 7 rh-sso7-keycloak rh-sso7-keycloak
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
GitHub 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-services
<24.0.0
24.0.0

Affected products

  • Red Hat Red Hat Build of Keycloak
  • Red Hat Red Hat Single Sign-On 7

Classification

Weakness
  • CWE-645 Overly Restrictive Account Lockout Mechanism
  • CWE-640 Weak Password Recovery Mechanism for Forgotten Password

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.