Skip to content

Keycloak vulnerable to Plaintext Storage of User Password

High severity GitHub Reviewed Published Sep 12, 2023 in keycloak/keycloak • Updated Nov 11, 2023

Package

maven org.keycloak:keycloak-core (Maven)

Affected versions

= 22.0.2

Patched versions

22.0.3

Description

A flaw was discovered in Keycloak Core package. When a user registers itself through registration flow, the "password" and "password-confirm" field from the form will occur as regular attributes in the users attributes. The password is also created, but the user attributes must not be there. This way, any entities (all users and clients with proper rights/roles) are able to retrieve the users passwords in clear-text.

Impact

Passwords for self-registered users are stored as cleartext attributes associated with the user.

Mitigation

Disable self-registration for users in all realms until patched.

References

@abstractj abstractj published to keycloak/keycloak Sep 12, 2023
Published by the National Vulnerability Database Sep 12, 2023
Published to the GitHub Advisory Database Sep 12, 2023
Reviewed Sep 12, 2023
Last updated Nov 11, 2023

Severity

High

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
High
Integrity
High
Availability
High

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:H/I:H/A:H

EPSS score

0.144%
(51st percentile)

Weaknesses

CVE ID

CVE-2023-4918

GHSA ID

GHSA-5q66-v53q-pm35

Source code

Credits

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