github.com/rancher/rancher
Affected
- introduced
2.6.0, fixed2.6.3(semver)
Fixed versions
2.6.3
Fix
- Fixed version
2.6.3go get github.com/rancher/[email protected]
Advisory
Also known as: CVE-2021-36778
Exposure of repository credentials to external third-party sources in Rancher
Impact
This issue only happens when the user configures access credentials to a private repository in Rancher inside Apps & Marketplace > Repositories. It affects Rancher versions 2.5.0 up to and including 2.5.11 and from 2.6.0 up to and including 2.6.2.
An insufficient check of the same-origin policy when downloading Helm charts from a configured private repository can lead to exposure of the repository credentials to a third-party provider. This exposure happens when the private repository:
The address of the private repository is not leaked, only the credentials are leaked in the HTTP Authorization header in base64 format.
With the patched versions, the default behavior now is to only send the private repository credentials when subdomain or domain hostname match when following the redirect or downloading external resources.
Patches
Patched versions include releases 2.5.12, 2.6.3 and later versions.
Workarounds
References
Information about the same-origin check and how to disable it is available in Rancher documentation.
For more information
If you have any questions or comments about this advisory:
High Basis: The source's own band: HIGH
2.6.0, fixed 2.6.3 (semver)2.6.3
2.6.3go get github.com/rancher/[email protected]2.5.0, fixed 2.5.12 (semver)2.5.12
2.5.12go get github.com/rancher/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0