Rancher: Cross-tenant BundleDeployment and Secret disclosure via spoofed cluster labels during agent-initiated registration in Fleet
What fixes it
- 0.16.1RancherCVE List
- 0.15.6RancherCVE List
- 0.14.10RancherCVE List
- 0.13.15RancherCVE List
- 0.12.19RancherCVE List
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
A cross-tenant authorization issue was discovered in SUSE Rancher Fleet. During agent-initiated cluster registration, cluster labels supplied by the registering agent, including labels in the reserved management.cattle.io/ namespace such as the cluster display name label, were applied to the resulting upstream Cluster object. Because Fleet resolves GitRepo and Bundle targets from those cluster labels, a party able to register a cluster into a Fleet workspace namespace shared with other tenants could cause its own cluster to satisfy targeting rules that administrators intended for a different cluster. This affects SUSE Rancher Fleet 0.16 before 0.16.1, 0.15 before 0.15.6, 0.14 before 0.14.10, 0.13 before 0.13.15, 0.12 before 0.12.19 and older versions.
Text from GitHub Advisory Database
Affected versions 10
- Rancheraffected: 0.16.0 before 0.16.1CVE List
- Rancheraffected: 0.15.0 before 0.15.6CVE List
- Rancheraffected: 0.14.0 before 0.14.10CVE List
- Rancheraffected: 0.13.0 before 0.13.15CVE List
- Rancheraffected: 0.12.0 before 0.12.19CVE List
- github.com/rancher/fleet, go>=v0.16.0, <v0.16.1GitHub
- github.com/rancher/fleet, go>=v0.15.0, <v0.15.6GitHub
- github.com/rancher/fleet, go>=v0.14.0, <v0.14.10GitHub
- github.com/rancher/fleet, go>=v0.13.0, <v0.13.15GitHub
- github.com/rancher/fleet, go>=v0.12.0, <v0.12.19GitHub