Helm impersonation bypass of `RESTClientGetter` retains `cluster-admin` during template rendering
- 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.1, 0.14.5, 0.13.10, 0.12.14, 0.11.13
- 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
Fleet's Helm deployer did not fully apply ServiceAccount impersonation in two code paths, allowing a tenant with git push access to a Fleet-monitored repository to read secrets from any namespace on every downstream cluster targeted by their `GitRepo`.
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.1; From 0.14.0 · fixed in 0.14.5; From 0.13.0 · fixed in 0.13.10; From 0.12.0 · fixed in 0.12.14; From 0.11.0 · fixed in 0.11.13
- github.com/rancher/fleetGo
From 0.15.0 · fixed in 0.15.1
- github.com/rancher/fleetGo
From 0.14.0 · fixed in 0.14.5
- github.com/rancher/fleetGo
From 0.13.0 · fixed in 0.13.10
- github.com/rancher/fleetGo
From 0.12.0 · fixed in 0.12.14
- github.com/rancher/fleetGo
From 0.11.0 · fixed in 0.11.13
- github.com/rancher/fleetGo
From 0.11.0 · fixed in 0.11.13; From 0.12.0 · fixed in 0.12.14; From 0.13.0 · fixed in 0.13.10; From 0.14.0 · fixed in 0.14.5; From 0.15.0 · fixed in 0.15.1