Description

Rancher Backup Operator pod's logs leak S3 tokens

Impact

A vulnerability has been identified within the Rancher Backup Operator, resulting in the leakage of S3 tokens (both accessKey and secretKey) into the rancher-backup-operator pod's logs.

Specifically, the S3 accessKey and secretKey are exposed in the pod's logs under the following logging level conditions:

Note: The S3 accessKey is exposed in the logs without requiring any supplementary configuration.

For further information on this attack category, please consult the associated MITRE ATT&CK - Technique - Log Enumeration.

Patches

This vulnerability is addressed by applying redaction to sensitive information that was leaking.

Patched versions of Rancher Backup Operator include: 108.0.1+up9.0.1, 107.1.2+up8.1.2, 106.0.6+up7.0.5, and 105.0.6+up6.0.3.

Workarounds

Users are advised to rotate both S3 accessKey and secretKey once they have upgraded to a fixed version, especially if logs are exported.

Users who cannot update Rancher are advised to refresh the Rancher app Repository, which should provide the ability to update just the Rancher Backup chart alone. This will patch the vulnerabilities without requiring Rancher to be updated. This will not work for Rancher clusters in an air-gap setup.

For air-gapped Rancher clusters, the Rancher version must be updated first, and then after you will find the patched version of the Rancher Backup chart to upgrade. You will also need to sync new images for the release to your image mirror.

Users who cannot update either Rancher or Rancher Backup should ensure that both debug and trace values are both false (default). Users should revert the values to the default until they can update to prevent potential leaks.

References

If you have any questions or comments about this advisory:

Reach out to the SUSE Rancher Security team for security related inquiries.

Open an issue in the Rancher repository.

Verify with our support matrix and product support lifecycle.

Mitigation

Aliases

References