Fleet has PSS Bypass through addLabelsFromOptions in Fleet Agent
SUSE Rancher
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/rancher/fleet Go |
|
|
SUSE Rancher
| Product | Affected | Fixed in |
|---|---|---|
| github.com/rancher/fleet Go |
|
|
A vulnerability has been identified in Fleet's agent-side deployer, which did not filter security-sensitive keys from namespaceLabels in fleet.yaml (or BundleDeployment.spec.options.namespaceLabels) when applying them to the target namespace.
An attacker with git push access to a Fleet-monitored repository could overwrite Pod Security Standards (PSS) enforcement labels on a target namespace. This allows the attacker to weaken admission controls and deploy workloads that PSS policies would otherwise block.
From the CVE record · suse
Fleet’s agent-side deployer does not filter security-sensitive namespace labels supplied through fleet.yaml or BundleDeployment options. An attacker with git push access to a Fleet-monitored repository can overwrite Pod Security Standards enforcement labels on a target namespace, weakening admission controls and deploying workloads those policies would otherwise block.
Teams running SUSE Rancher Fleet with github.com/rancher/fleet versions >=0.15.0 <0.15.2, >=0.14.0 <0.14.6, >=0.13.0 <0.13.11, or >=0.12.0 <0.12.15 should check their deployments.