github.com/rancher/rancher
Affected
- introduced
2.6.0, fixed2.6.13(semver)
Fixed versions
2.6.13
Fix
- Fixed version
2.6.13go get github.com/rancher/[email protected]
Advisory
Also known as: CVE-2020-10676
Rancher users retain access after moving namespaces into projects they don't have access to
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:
High Basis: The source's own band: HIGH
2.6.0, fixed 2.6.13 (semver)2.6.13
2.6.13go get github.com/rancher/[email protected]2.7.0, fixed 2.7.4 (semver)2.7.4
2.7.4go get github.com/rancher/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0