Rancher Fleet SSRF in Bundle Reader via Unvalidated Helm Repository URL in fleet.yaml
SUSE Rancher
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/rancher/fleet Go |
|
|
SUSE Rancher
| Product | Affected | Fixed in |
|---|---|---|
| github.com/rancher/fleet Go |
|
|
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.
From the CVE record · suse
When helmRepoURLRegex is unset on a GitRepo resource, Fleet's bundle reader can forward Helm BasicAuth credentials to any URL in the helm.repo field of a fleet.yaml file. An attacker who can push to a Fleet-monitored Git repository can use this to leak Helm access credentials; the input does not specify whether further user interaction is needed.
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.