CyberRota Analysis
AI-GeneratedA vulnerability exists in the User-Managed Access (UMA) implementation of Keycloak, specifically in the authorization token endpoint, where permission tickets from different users can be incorrectly merged if they own resources with the same name. This flaw could allow an attacker to gain unauthorized access to a victim's resource by exploiting the merged permissions. Organizations using Keycloak for resource management should prioritize addressing this issue to prevent potential unauthorized access to sensitive data.
Original NVD 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.