Skip to content

Keycloak vulnerable to session hijacking via re-authentication

Moderate severity GitHub Reviewed Published Apr 17, 2024 in keycloak/keycloak • Updated Apr 25, 2024

Package

maven org.keycloak:keycloak-services (Maven)

Affected versions

< 22.0.10
>= 23.0.0, < 24.0.3

Patched versions

22.0.10
24.0.3

Description

A flaw was found in Keycloak. An active keycloak session can be hijacked by initiating a new authentication (having the query parameter prompt=login) and forcing the user to enter his credentials once again. If the user cancels this re-authentication by clicking Restart login, the account takeover could take place as the new session, with a different SUB, will have the same SID as the previous session.

References

@abstractj abstractj published to keycloak/keycloak Apr 17, 2024
Published to the GitHub Advisory Database Apr 17, 2024
Reviewed Apr 17, 2024
Published by the National Vulnerability Database Apr 25, 2024
Last updated Apr 25, 2024

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
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:N/UI:R/S:U/C:N/I:H/A:N

EPSS score

0.045%
(16th percentile)

Weaknesses

CVE ID

CVE-2023-6787

GHSA ID

GHSA-c9h6-v78w-52wj

Source code

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