Rancher Fleet SSRF in Bundle Reader via Unvalidated Helm Repository URL in fleet.yaml
- 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: partial
Summary
Missing filtering when the helmRepoURLRegex field isn't set on a GitRepo resource in SUSE Rancher Fleet's bundle reader in 0.15 before 0.15.2, 0.14 before 0.14.6, 0.13 before 0.13.11 and 0.12 before 0.12.15 forwards Helm authentication credentials (BasicAuth) to any URL specified in the helm.repo field of a fleet.yaml file, allowing attackers able to push to fleet monitored git repos to leak helm access credentials.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- 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.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
- 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