Keycloak-services: keycloak-services: stateless token preferred_username fallback enables identity rebinding

Overview

A flaw was found in the TokenManager component of Keycloak, an open-source identity and access management solution. The issue occurs during the validation of stateless access tokens when the original user ID no longer exists. Keycloak incorrectly falls back to using the username to identify the user without verifying if the identity matches the original token subject. This could allow an attacker with an old token to gain access to a newly created service account if it shares the same client ID as a previously deleted one.

Affected

• keycloak-services (all versions)
• rhbk/keycloak-rhel9 (all versions)
• keycloak-services

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

Workarounds

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.