Rancher doesn't properly sanitize credentials in cluster template answers

Overview

Impact

It was discovered that in Rancher versions up to and including 2.5.12 and 2.6.3 there is a failure to properly sanitize credentials in cluster template answers. This failure can lead to plaintext storage and exposure of credentials, passwords and API tokens.

The exposed credentials are visible in Rancher to authenticated Cluster Owners, Cluster Members, Project Owners and Project Members on the endpoints /v1/management.cattle.io.clusters, /v3/clusters and /k8s/clusters/local/apis/management.cattle.io/v3/clusters.

Sensitive fields are now stripped from Clusters objects before the object is stored. For objects that existed before this security fix, a one-time migration happens on startup.

Important:

• It is highly advised to review for potential leaked credentials in this scenario, and to change them if deemed necessary.
• The final impact severity for confidentiality, integrity and availability is dependent on the permissions that the leaked credentials have on their own services.

Patches

Patched versions include releases 2.5.13, 2.6.4 and later versions.

Workarounds

Limit access in Rancher to trusted users. There is not a direct mitigation besides upgrading to the patched Rancher versions.

Important: It is highly advised to review for potential leaked credentials in this scenario, and to change them if deemed necessary.

For more information

If you have any questions or comments about this advisory:

• Reach out to SUSE Rancher Security team for security related inquiries.
• Open an issue in Rancher repository.
• Verify our support matrix and product support lifecycle.

Affected packages

• github.com/rancher/rancher >= 2.5.0, < 2.5.13
• github.com/rancher/rancher >= 2.6.0, < 2.6.4

Remediation

Upgrade to a patched release:

• github.com/rancher/rancher 2.5.13
• github.com/rancher/rancher 2.6.4