Keycloak-services: keycloak-services: uma scope merge across resource owners via resource name collision
Red Hat build of Keycloak 26.6.8 · Red Hat Single Sign-On 7
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Red Hat build of Keycloak 26.6.8 | — | No fix yet |
| Red Hat Red Hat build of Keycloak 26.6.8 | — | No fix yet |
| Red Hat Red Hat build of Keycloak 26.6.8 | — | No fix yet |
| Red Hat Red Hat Single Sign-On 7 | — | No fix yet |
Original description
A flaw was found in the User-Managed Access (UMA) implementation of Keycloak. The issue occurs in the authorization token endpoint when processing permission tickets. If two different users own resources with the same name, the system incorrectly merges the permissions from both resources when one user requests an authorization token. This allows an attacker to gain access scopes on a victim's resource that were never intended to be shared.
From the CVE record · redhat