Keycloak-services: keycloak-services: stateless token preferred_username fallback enables identity rebinding
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Red Hat | Build of Keycloak | ||
| Red Hat | Single Sign-On |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Red Hat, strongest first
Embed
A live severity badge for an advisory, README or ticket