Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-4629: A vulnerability was found in Keycloak

47
This month
MEDIUM 6.5REMOTEWATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2024-4629 is a medium-severity flaw (CVSS 6.5) affecting keycloak, build of keycloak, single sign-on. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.8% (top 44%)
CISA exploited listNo
WeaknessCWE-837
Published2024-09-03
Last modified2026-06-17
Publisher (CNA): Red Hat, Inc. · Vendor: redhat

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

redhat keycloak UPGRADE
Affected: < 24.0.3
Fixed in: 24.0.3
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy keycloak || rpm -q keycloak || keycloak --version
2. UPGRADE to 24.0.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade keycloak
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade keycloak
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
redhat build of keycloak UPGRADE
Affected: >= 22.0 and < 22.012
Fixed in: 22.012
Safe to downgrade to: a release before 22.0
1. Check installed version
apt-cache policy build-of-keycloak || rpm -q build-of-keycloak || build-of-keycloak --version
2. UPGRADE to 22.012 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade build-of-keycloak
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade build-of-keycloak
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 22.0 (Debian / Ubuntu)
apt-cache madison build-of-keycloak sudo apt install build-of-keycloak=<VERSION_BEFORE_22.0> sudo apt-mark hold build-of-keycloak
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list build-of-keycloak sudo dnf downgrade build-of-keycloak-<VERSION_BEFORE_22.0> sudo dnf versionlock add build-of-keycloak
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
redhat single sign-on UPGRADE
Affected: all versions · >= 7.6 and < 7.6.10
Fixed in: 7.6.10
Safe to downgrade to: a release before 7.6
1. Check installed version
apt-cache policy single-sign-on || rpm -q single-sign-on || single-sign-on --version
2. UPGRADE to 7.6.10 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade single-sign-on
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade single-sign-on
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 7.6 (Debian / Ubuntu)
apt-cache madison single-sign-on sudo apt install single-sign-on=<VERSION_BEFORE_7.6> sudo apt-mark hold single-sign-on
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list single-sign-on sudo dnf downgrade single-sign-on-<VERSION_BEFORE_7.6> sudo dnf versionlock add single-sign-on
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
redhat openshift container platform DOWNGRADE
Affected: 4.11 · 4.12
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.11
1. Check installed version
apt-cache policy openshift-container-platform || rpm -q openshift-container-platform || openshift-container-platform --version
2. No fixed release: DOWNGRADE to a release before 4.11 (Debian / Ubuntu)
apt-cache madison openshift-container-platform sudo apt install openshift-container-platform=<VERSION_BEFORE_4.11> sudo apt-mark hold openshift-container-platform
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list openshift-container-platform sudo dnf downgrade openshift-container-platform-<VERSION_BEFORE_4.11> sudo dnf versionlock add openshift-container-platform
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
redhat openshift container platform for linuxone DOWNGRADE
Affected: 4.9 · 4.10
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.9
1. Check installed version
apt-cache policy openshift-container-platform-for-linuxone || rpm -q openshift-container-platform-for-linuxone || openshift-container-platform-for-linuxone --version
2. No fixed release: DOWNGRADE to a release before 4.9 (Debian / Ubuntu)
apt-cache madison openshift-container-platform-for-linuxone sudo apt install openshift-container-platform-for-linuxone=<VERSION_BEFORE_4.9> sudo apt-mark hold openshift-container-platform-for-linuxone
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list openshift-container-platform-for-linuxone sudo dnf downgrade openshift-container-platform-for-linuxone-<VERSION_BEFORE_4.9> sudo dnf versionlock add openshift-container-platform-for-linuxone
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
redhat openshift container platform for power DOWNGRADE
Affected: 4.9 · 4.10
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.9
1. Check installed version
apt-cache policy openshift-container-platform-for-power || rpm -q openshift-container-platform-for-power || openshift-container-platform-for-power --version
2. No fixed release: DOWNGRADE to a release before 4.9 (Debian / Ubuntu)
apt-cache madison openshift-container-platform-for-power sudo apt install openshift-container-platform-for-power=<VERSION_BEFORE_4.9> sudo apt-mark hold openshift-container-platform-for-power
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list openshift-container-platform-for-power sudo dnf downgrade openshift-container-platform-for-power-<VERSION_BEFORE_4.9> sudo dnf versionlock add openshift-container-platform-for-power
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-4629?

keycloak: upgrade to 24.0.3; build of keycloak: upgrade to 22.012; single sign-on: upgrade to 7.6.10. Exact commands for each OS are on this page.

Is CVE-2024-4629 being exploited?

CVE-2024-4629 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-4629 affect?

CVE-2024-4629 affects keycloak, build of keycloak, single sign-on. Severity is medium (CVSS 6.5). 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

How urgent is CVE-2024-4629?

Priority 47/100. Remotely exploitable, no login, no user action; On your watchlist

Software pages

Keycloak vulnerabilities · Red Hat OpenShift vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.