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.
Patched versions include releases 2.5.12, 2.6.3 and later versions.
Information about the same-origin check and how to disable it is available in Rancher documentation.
If you have any questions or comments about this advisory: