CVE-2020-10676
First published: Tue Jun 06 2023(Updated: )
### 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](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-resources-setup/secrets#creating-secrets-in-projects)). In addition, resources in the namespace will now count toward the [quota limit](https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/about-project-resource-quotas) 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](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/).
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| SUSE Rancher | >=2.0.0<2.6.13 | |
| SUSE Rancher | >=2.7.0<2.7.4 | |
| go/github.com/rancher/rancher | >=2.7.0<2.7.4 | 2.7.4 |
| go/github.com/rancher/rancher | >=2.6.0<2.6.13 | 2.6.13 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://forums.rancher.com/c/announcements
- https://github.com/advisories/GHSA-8vhc-hwhc-cpj4 (Advisory)
- https://github.com/rancher/rancher/releases/tag/v2.6.13
- https://github.com/rancher/rancher/releases/tag/v2.7.4
- https://github.com/rancher/rancher/security/advisories/GHSA-8vhc-hwhc-cpj4
- https://nvd.nist.gov/vuln/detail/CVE-2020-10676
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.
- collector/nvd-api
- collector/github-advisory-latest
- alias/GHSA-8vhc-hwhc-cpj4
- alias/CVE-2020-10676
- agent/references
- agent/author
- agent/type
- agent/first-publish-date
- agent/softwarecombine
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup
- collector/github-advisory
- source/GitHub
- agent/weakness
- agent/severity
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/description
- agent/trending
- agent/tags
- agent/source
- vendor/suse
- canonical/suse rancher
- version/suse rancher/2.0.0
- version/suse rancher/2.7.0
- package-manager/go