CVE-2020-10676: High severity SUSE rancher vulnerability
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.
Other sources
In Rancher 2.x before 2.6.13 and 2.7.x before 2.7.4, an incorrectly applied authorization check allows users who have certain access to a namespace to move that namespace to a different project.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2020-10676?
CVE-2020-10676 is considered a high severity vulnerability due to the potential unauthorized access it allows.
How do I fix CVE-2020-10676?
To fix CVE-2020-10676, update SUSE Rancher to version 2.6.13 or 2.7.4.
What are the affected versions for CVE-2020-10676?
CVE-2020-10676 affects SUSE Rancher versions between 2.0.0 to 2.6.13 and 2.7.0 to 2.7.4.
What impact does CVE-2020-10676 have on user permissions?
CVE-2020-10676 allows users with update privileges to preserve their permissions after a namespace transfer to a project they shouldn't access.
Is there a known exploit for CVE-2020-10676?
There are no specific publicly disclosed exploits for CVE-2020-10676, but the vulnerability poses a significant risk if unaddressed.