VulnerabilityPublished 18 Jun 2024Updated 26 Mar 2026

CVE-2024-5967: keycloak · Incorrect Default Permissions

Affects keycloakSource CVE Database V5

Not known to be exploited · CVSS 2.7 Low.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

2.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavenorg.keycloak/keycloak`pkg:maven/org.keycloak/keycloak`Other threats	Affected =0 =23.0.0 =25.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-5967, organizations should: 1) Immediately update Keycloak to a patched version once available from the vendor or community. 2) Restrict and monitor administrative access to the Keycloak console, enforcing strong authentication methods such as multi-factor authentication (MFA) and least privilege principles. 3) Audit and limit the number of users with 'manage-realm' permissions to reduce the attack surface. 4) Implement network segmentation and firewall rules to restrict outbound LDAP connections from Keycloak servers to only trusted LDAP hosts. 5) Monitor Keycloak logs and network traffic for unusual LDAP connection attempts or changes to LDAP configuration. 6) Rotate LDAP bind credentials regularly and after any suspected compromise. 7) Consider additional application-layer controls or web application firewalls (WAF) to detect and block unauthorized configuration changes. These steps go beyond generic advice by focusing on access control, monitoring, and network restrictions specific to the nature of this vulnerability.

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.

Impact

The primary impact of CVE-2024-5967 is the potential leakage of LDAP bind credentials, which are often domain-level credentials with broad access rights. If an attacker obtains these credentials, they can impersonate legitimate users or services within the domain, leading to unauthorized access, data exfiltration, lateral movement, and further compromise of enterprise networks. Organizations relying on Keycloak for identity federation and LDAP integration are at risk, especially if administrative accounts are compromised or insufficiently protected. The vulnerability does not directly affect system availability or integrity but significantly undermines confidentiality. The scope of impact is limited to environments where Keycloak is deployed with LDAP integration and where attackers can gain or already have administrative privileges. This threat is particularly critical in large enterprises, government agencies, and cloud service providers that use Keycloak for centralized authentication and authorization.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 18:27 UTC

Technical details

References

Community reviews

Related threats