A flaw was found in the Keycloak organization feature, which allows the incorrect assignment of an organization to a user if their username or email matches the organization’s domain pattern. This issue occurs at the mapper level, leading to misrepresentation in tokens. If an application relies on these claims for authorization, it may incorrectly assume a user belongs to an organization they are not a member of, potentially granting unauthorized access or privileges.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Build of Keycloak | RedHat | keycloak-services | * |
| Red Hat build of Keycloak 26.0 | RedHat | rhbk/keycloak-operator-bundle:26.0.10-3 | * |
| Red Hat build of Keycloak 26.0 | RedHat | rhbk/keycloak-rhel9:26.0-11 | * |
| Red Hat build of Keycloak 26.0 | RedHat | rhbk/keycloak-rhel9-operator:26.0-12 | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: