Skip to content

Duplicate Advisory: Authentication Bypass Due to Missing LDAP Bind After Password Reset in Keycloak

Moderate severity GitHub Reviewed Published Jan 22, 2025 to the GitHub Advisory Database • Updated Mar 10, 2025
Withdrawn This advisory was withdrawn on Mar 10, 2025

Package

maven org.keycloak:keycloak-ldap-federation (Maven)

Affected versions

<= 26.1.0

Patched versions

None

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-2p82-5wwr-43cw. This link is maintained to preserve external references.

Original Description

A flaw was found in Keycloak. When an Active Directory user resets their password, the system updates it without performing an LDAP bind to validate the new credentials against AD. This vulnerability allows users whose AD accounts are expired or disabled to regain access in Keycloak, bypassing AD restrictions. The issue enables authentication bypass and could allow unauthorized access under certain conditions.

References

Published by the National Vulnerability Database Jan 22, 2025
Published to the GitHub Advisory Database Jan 22, 2025
Reviewed Jan 22, 2025
Withdrawn Mar 10, 2025
Last updated Mar 10, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

EPSS score

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-m3hp-8546-5qmr

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.