Rancher users retain access after moving namespaces into projects they don't have access to

Overview

Impact

A vulnerability was identified in which users with update privileges on a namespace, can move that namespace into a project they don't have access to. After the namespace transfer is completed, their previous permissions are still preserved, which enables them to gain access to project-specific resources (such as project secrets). In addition, resources in the namespace will now count toward the quota limit of the new project, potentially causing availability issues.

User with roles Project Owner and Project Member on the source project can exploit this vulnerability; however, this would also apply to custom roles with similar privileges.

The patched version include an improved RBAC mechanism, which checks if the user has the correct permissions before the namespace move takes place.

Patches

Patched versions include releases 2.6.13, 2.7.4 and later versions.

Workarounds

There is no direct mitigation besides updating Rancher to a patched version.

For more information

If you have any questions or comments about this advisory:

• Reach out to the SUSE Rancher Security team for security related inquiries.
• Open an issue in the Rancher repository.
• Verify with our support matrix and product support lifecycle.

Affected packages

• github.com/rancher/rancher >= 2.6.0, < 2.6.13
• github.com/rancher/rancher >= 2.7.0, < 2.7.4

Remediation

Upgrade to a patched release:

• github.com/rancher/rancher 2.6.13
• github.com/rancher/rancher 2.7.4