LDAP credential disclosure via reused secret placeholder
Published Jun 18, 2024 · Updated Mar 26, 2026
Credential disclosure in Keycloak 24.0.5 and earlier and 25.0.0 allows remote authenticated users to obtain stored LDAP bind credentials. The LDAP test path replaces a submitted secret placeholder with the stored bind credential without first requiring the submitted URL and bind DN to match the saved component. An administrator with manage-realm permission can point the test at an attacker-controlled LDAP server, causing Keycloak to authenticate to it with the domain credential.
Summary
What happened
Credential disclosure in Keycloak 24.0.5 and earlier and 25.0.0 allows remote authenticated users to obtain stored LDAP bind credentials. The LDAP test path replaces a submitted secret placeholder with the stored bind credential without first requiring the submitted URL and bind DN to match the saved component. An administrator with manage-realm permission can point the test at an attacker-controlled LDAP server, causing Keycloak to authenticate to it with the domain credential.
The record
- CVE
- CVE-2024-5967
- Published
- Jun 18, 2024
- Updated
- Mar 26, 2026
- Vendor
- Red Hat
- Product
- RHEL-8 based Middleware Containers
- Classifications
- CWE-276, T1555
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jun 18, 2024CVE publishedPublication date reported by the CVE source.
- Mar 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo