NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
LOW severity

CVE-2024-5967 — keycloak-ldap-federation

LOWFix: keycloak/keycloak@0d05300

CVE-2024-5967 is a low-severity (CVSS 2.7) Incorrect Default Permissions vulnerability in org.keycloak:keycloak-ldap-federation. A fix is available for org.keycloak:keycloak-ldap-federation — see the affected versions and patch details below.

Keycloak: leak of configured ldap bind credentials through the keycloak admin console

Also known asGHSA-c25h-c27q-5qpv
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-5967.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs51th percentile — riskier than 51% of all scored CVEsHighest risk
0.00%0.38%0.77%1.15%0.1%0.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
☕org.keycloak:keycloak-ldap-federation☕org.keycloak:keycloak-ldap-federation☕org.keycloak:keycloak-ldap-federation

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

The LDAP testing endpoint allows to change the Connection URL independently of and without having to re-enter the currently configured LDAP bind credentials. An attacker with admin access (permission manage-realm) can change the LDAP host URL ("Connection URL") to a machine they control. The Keycloak server will connect to the attacker's host and try to authenticate with the configured credentials, thus leaking them to the attacker. As a consequence, an attacker who has compromised the admin console/compromised a user with sufficient privileges can leak domain credentials and can now attack the domain.

Acknowledgements

Special thanks to Simon Wessling for reporting this issue and helping us improve our project

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.keycloak:keycloak-ldap-federation≥ 25.0.0&&< 25.0.125.0.1org.keycloak:keycloak-ldap-federation:25.0.1
☕Mavenorg.keycloak:keycloak-ldap-federationall versions22.0.12org.keycloak:keycloak-ldap-federation:22.0.12
☕Mavenorg.keycloak:keycloak-ldap-federation≥ 23.0.0&&< 24.0.624.0.6org.keycloak:keycloak-ldap-federation:24.0.6

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-ldap-federation, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.keycloak:keycloak-ldap-federation to 25.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-5967 is resolved across your whole dependency graph.

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow
Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2024-5967 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Build of Keycloakkeycloak-coreRHSA-2024:6501
Red Hat build of Keycloak 22rhbk/keycloak-operator-bundle:22.0.12-1RHSA-2024:6500
Red Hat Single Sign-On 7rh-sso7-keycloakRHSA-2024:6499
Red Hat Single Sign-On 7.6 for RHEL 7rh-sso7-keycloak-0:18.0.16-1.redhat_00001.1.el7ssoRHSA-2024:6493
Red Hat Single Sign-On 7.6 for RHEL 8rh-sso7-keycloak-0:18.0.16-1.redhat_00001.1.el8ssoRHSA-2024:6494
Red Hat Single Sign-On 7.6 for RHEL 9rh-sso7-keycloak-0:18.0.16-1.redhat_00001.1.el9ssoRHSA-2024:6495
RHEL-8 based Middleware Containersrh-sso-7/sso76-openshift-rhel8:7.6-52RHSA-2024:6497

Frequently Asked Questions

### Impact The LDAP testing endpoint allows to change the Connection URL independently of and without having to re-enter the currently configured LDAP bind credentials. An attacker with admin access (permission manage-realm) can change the LDAP host URL ("Connection URL") to a machine they control. The Keycloak server will connect to the attacker's host and try to authenticate with the configured credentials, thus leaking them to the attacker. As a consequence, an attacker who has compromised the admin console/compromised a user with sufficient privileges can leak domain credentials and can n
O3 Security · Impact-Aware SCA

Is CVE-2024-5967 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-5967: keycloak-ldap-federation — Fixed in 25.0.1