A privilege escalation flaw was found in the token exchange feature of keycloak. Missing authorization allows a client application holding a valid access token to exchange tokens for any target client by passing the client_id of the target. This could allow a client to gain unauthorized access to additional services.
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Keycloak | Redhat | * | 18.0.0 (excluding) |
Red Hat Single Sign-On 7 | RedHat | keycloak | * |
Red Hat Single Sign-On 7.5 for RHEL 7 | RedHat | rh-sso7-keycloak-0:15.0.6-1.redhat_00002.1.el7sso | * |
Red Hat Single Sign-On 7.5 for RHEL 8 | RedHat | rh-sso7-keycloak-0:15.0.6-1.redhat_00002.1.el8sso | * |
RHEL-8 based Middleware Containers | RedHat | rh-sso-7/sso75-openshift-rhel8:7.5-26 | * |
RHEL-8 based Middleware Containers | RedHat | rh-sso-7/sso7-rhel8-operator-bundle:7.5.2-8 | * |
Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user’s privileges and any permissions or other access-control specifications that apply to the resource. When access control checks are not applied, users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.