Skip to content

GHSA-gmrm-8fx4-66x7

Duplicate Advisory: Keycloak: Leak of configured LDAP bind credentials

Low Withdrawn Jun 21, 2024 Maven
Severity
2.7 / 10
Low · CVSS 3.1
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
CWE-276 Incorrect Default Permissions
Fix
None yet
No fixed version published

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-c25h-c27q-5qpv. This link is maintained to preserve external references.

Original 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 versions

Maven

PackageVulnerableFixed in
org.keycloak:keycloak-core
<= 24.0.5
No fix yet

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 3.1 2.7

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

Weakness

CWE-276: Incorrect Default Permissions

During installation, installed file permissions are set to allow anyone to modify those files.

How to prevent it
  • Architecture and Design, Operation: The architecture needs to access and modification attributes for files to only those users who actually require those actions.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Withdrawn
  3. Last updated by the source
AdvisorySeverityWhy it's related
GHSA-q4xq-445g-g6ch
Keycloak allows cross-site scripting (XSS)
Low Also affects org.keycloak:keycloak-core
GHSA-93ww-43rr-79v3
Keycloak mTLS Authentication Bypass via Reverse Proxy TLS Termination
High Also affects org.keycloak:keycloak-core
GHSA-w97f-w3hq-36g2
Keycloak Denial of Service vulnerability
High Also affects org.keycloak:keycloak-core
GHSA-xmmm-jw76-q7vg
Keycloaks's One Time Passcode (OTP) is valid longer than expiration timeSeverity
Medium Also affects org.keycloak:keycloak-core
GHSA-g4gc-rh26-m3p5
Keycloak Open Redirect vulnerability
Medium Also affects org.keycloak:keycloak-core
GHSA-9vm7-v8wj-3fqw
keycloak-core: open redirect via "form_post.jwt" JARM response mode
Medium Also affects org.keycloak:keycloak-core
GHSA-5q66-v53q-pm35
Keycloak vulnerable to Plaintext Storage of User Password
High Also affects org.keycloak:keycloak-core
GHSA-5cc8-pgp5-7mpm
Keycloak Untrusted Certificate Validation vulnerability
Medium Also affects org.keycloak:keycloak-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor