CVE-2023-22648

A bug has been identified in which permission changes in Azure AD are not reflected to users while they are logged in the Rancher UI. This would cause the users to retain their previous permissions in Rancher, even if they change groups on Azure AD, for example, to a lower privileged group, or are removed from a group, thus retaining their access to Rancher instead of losing it. ### Impact This issue only affects Rancher instances with Azure AD integration enabled, regardless of the [automatically refreshing settings](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/manage-users-and-groups#automatically-refreshing-user-information) which are enabled by default. The users that obtained a token (or kubeconfig) to access Rancher through the following sessions are affected by this issue: 1) Users using the Rancher UI. 2) Users using `kubectl` based on a `kubeconfig` downloaded through the Rancher UI. 3) Tokens created via the Rancher UI Create API Key feature. Note that the permission caching is persisted even when the Rancher Manager pod is restarted. The only way for a user to get the new permissions is to logout and login again. ### Patches Patched versions include releases `2.6.13`, `2.7.4` and later versions. ### For more information If you have any questions or comments about this advisory: - Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries. - Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository. - Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).

A bug has been identified in which permission changes in Azure AD are not reflected to users while they are logged in the Rancher UI. This would cause the users to retain their previous permissions in Rancher, even if they change groups on Azure AD, for example, to a lower privileged group, or are removed from a group, thus retaining their access to Rancher instead of losing it. ### Impact This issue only affects Rancher instances with Azure AD integration enabled, regardless of the [automatically refreshing settings](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/manage-users-and-groups#automatically-refreshing-user-information) which are enabled by default. The users that obtained a token (or kubeconfig) to access Rancher through the following sessions are affected by this issue: 1) Users using the Rancher UI. 2) Users using `kubectl` based on a `kubeconfig` downloaded through the Rancher UI. 3) Tokens created via the Rancher UI Create API Key feature. Note that the permission caching is persisted even when the Rancher Manager pod is restarted. The only way for a user to get the new permissions is to logout and login again. ### Patches Patched versions include releases `2.6.13`, `2.7.4` and later versions. ### For more information If you have any questions or comments about this advisory: - Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries. - Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository. - Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).

Una vulnerabilidad de gestión de privilegios incorrecta en SUSE Rancher causa que los cambios de permisos en Azure AD no se reflejen a los usuarios mientras están conectados a la interfaz de usuario de Rancher. Esto causaría que los usuarios retengan sus permisos anteriores en Rancher, incluso si cambian de grupo en Azure AD, por ejemplo, a un grupo con privilegios inferiores, o son eliminados de un grupo, reteniendo así su acceso a Rancher en lugar de perderlo. Este problema afecta a Rancher: desde >= 2.6.7 antes de anterior a 2.6.13, desde >= 2.7.0 antes de anterior a 2.7.4.