CVE-2024-5967 — keycloak-ldap-federation
LOWCVE-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
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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-5967 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.keycloak:keycloak-ldap-federation☕org.keycloak:keycloak-ldap-federation☕org.keycloak:keycloak-ldap-federationReal-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
A vulnerability was found in Keycloak. The LDAP testing endpoint allows changing the Connection URL independently without re-entering the currently configured LDAP bind credentials. This flaw allows an attacker with admin access (permission manage-realm) to 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 or compromised a user with sufficient privileges can leak domain credentials and attack the domain.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.keycloak:keycloak-ldap-federation | ≥ 25.0.0&&< 25.0.1 | 25.0.1org.keycloak:keycloak-ldap-federation:25.0.1 |
| ☕Maven | org.keycloak:keycloak-ldap-federation | all versions | 22.0.12org.keycloak:keycloak-ldap-federation:22.0.12 |
| ☕Maven | org.keycloak:keycloak-ldap-federation | ≥ 23.0.0&&< 24.0.6 | 24.0.6org.keycloak:keycloak-ldap-federation:24.0.6 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
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.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-5967 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-5967. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Build of Keycloak | keycloak-core | RHSA-2024:6501 |
| Red Hat build of Keycloak 22 | rhbk/keycloak-operator-bundle:22.0.12-1 | RHSA-2024:6500 |
| Red Hat Single Sign-On 7 | rh-sso7-keycloak | RHSA-2024:6499 |
| Red Hat Single Sign-On 7.6 for RHEL 7 | rh-sso7-keycloak-0:18.0.16-1.redhat_00001.1.el7sso | RHSA-2024:6493 |
| Red Hat Single Sign-On 7.6 for RHEL 8 | rh-sso7-keycloak-0:18.0.16-1.redhat_00001.1.el8sso | RHSA-2024:6494 |
| Red Hat Single Sign-On 7.6 for RHEL 9 | rh-sso7-keycloak-0:18.0.16-1.redhat_00001.1.el9sso | RHSA-2024:6495 |
| RHEL-8 based Middleware Containers | rh-sso-7/sso76-openshift-rhel8:7.6-52 | RHSA-2024:6497 |
Frequently Asked Questions
Is CVE-2024-5967 in your dependencies?
O3 Security finds CVE-2024-5967 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.