This vulnerability only affects customers using the
restricted-admin role in Rancher. For this role to be active, Rancher must be bootstrapped with the environment variable
CATTLE_RESTRICTED_DEFAULT_ADMIN=true or the configuration flag
A flaw was discovered in Rancher versions from 2.5.0 up to and including 2.5.12 and from 2.6.0 up to and including 2.6.3 where the
global-data role in
cattle-global-data namespace grants write access to the Catalogs. Since each user with any level of catalog access was bound to the
global-data role, this grants write access to templates (
CatalogTemplates) and template versions (
CatalogTemplateVersions) for any user with any level of catalog access. New users created in Rancher are by default assigned to the
user role (standard user), which is not designed to grant write catalog access. This vulnerability effectively elevates the privilege of any user to write access for the catalog template and catalog template version resources.
A malicious user could abuse this vulnerability to:
icon) of an application or template to an arbitrary image.
versionDirfield. When a user on the target cluster deploys their chart, it will deploy the modified version.
This vulnerability does not allow to modify the base64 encoded
files fields of the
templateVersions, so one cannot inject arbitrary data to charts that have already been pulled from their respective catalog.
Without access to the Catalog, malicious users are limited to injecting apps which already exist in a registered catalog. They would need write access to the catalog or external write access to a source repo to inject arbitrary code.
Patched versions include releases 2.5.13, 2.6.4 and later versions.
Limit access in Rancher to trusted users. There is not a direct mitigation besides upgrading to the patched Rancher versions.
Note: If you use the
restricted-admin as the default admin role in your environment, it's highly advised to review
CatalogTemplateVersions for possible malicious modifications.
If you have any questions or comments about this advisory: * Reach out to SUSE Rancher Security team for security related inquiries. * Open an issue in Rancher repository. * Verify our support matrix and product support lifecycle.