Fleet has PSS Bypass through addLabelsFromOptions in Fleet Agent
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.15.2, 0.14.6, 0.13.11, 0.12.15
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- Record last updated
Affected versions
- github.com/rancher/fleet
From 0.15.0 · fixed in 0.15.2; From 0.14.0 · fixed in 0.14.6; From 0.13.0 · fixed in 0.13.11; From 0.12.0 · fixed in 0.12.15
- github.com/rancher/fleetGo
From 0.12.0 · fixed in 0.12.15; From 0.13.0 · fixed in 0.13.11; From 0.14.0 · fixed in 0.14.6; From 0.15.0 · fixed in 0.15.2
- github.com/rancher/fleetGo
From 0.15.0 · fixed in 0.15.2
- github.com/rancher/fleetGo
From 0.14.0 · fixed in 0.14.6
- github.com/rancher/fleetGo
From 0.13.0 · fixed in 0.13.11
- github.com/rancher/fleetGo
From 0.12.0 · fixed in 0.12.15