github.com/rancher/rancher
Affected
- introduced
2.5.0, fixed2.5.17(semver)
Fixed versions
2.5.17
Fix
- Fixed version
2.5.17go get github.com/rancher/[email protected]
Advisory
Also known as: CVE-2022-43757
Plaintext storage of sensitive data in Rancher API and cluster.management.cattle.io objects
Impact
This issue affects Rancher versions from 2.5.0 up to and including 2.5.16, from 2.6.0 up to and including 2.6.9 and 2.7.0. It was discovered that the security advisory CVE-2021-36782 (GHSA-g7j7-h4q8-8w2f), previously released by Rancher, missed addressing some sensitive fields, secret tokens, encryption keys, and SSH keys that were still being stored in plaintext directly on Kubernetes objects like Clusters.
The exposed credentials are visible in Rancher to authenticated Cluster Owners, Cluster Members, Project Owners and Project Members of that cluster on the endpoints:
/v1/management.cattle.io.cluster/v1/management.cattle.io.clustertemplaterevisionsThe remaining sensitive fields are now stripped from Clusters and other objects and moved to a Secret before the object is stored. The Secret is retrieved when the credential is needed. For objects that existed before this security fix, a one-time migration happens on startup.
The fields that have been addressed by this security fix are:
Cluster.Spec.RancherKubernetesEngineConfig.Services.KubeAPI.SecretsEncryptionConfig.CustomConfig.Providers[].AESGCM.Keys[].SecretCluster.Spec.RancherKubernetesEngineConfig.Services.KubeAPI.SecretsEncryptionConfig.CustomConfig.Providers[].AESCBC.Keys[].SecretCluster.Spec.RancherKubernetesEngineConfig.Services.KubeAPI.SecretsEncryptionConfig.CustomConfig.Providers[].SecretboxConfiguration.Keys[].SecretCluster.Spec.RancherKubernetesEngineConfig.Services.Kubelet.ExtraEnv when containing the AWS_SECRET_ACCESS_KEY environment variableCluster.Spec.RancherKubernetesEngineConfig.BastionHost.SSHKeyCluster.Spec.RancherKubernetesEngineConfig.PrivateRegistries[].ECRCredentialPlugin.AwsSecretAccessKeyCluster.Spec.RancherKubernetesEngineConfig.PrivateRegistries[].ECRCredentialPlugin.AwsSessionTokenCluster.Spec.RancherKubernetesEngineConfig.Network.AciNetworkProvider.ApicUserKeyCluster.Spec.RancherKubernetesEngineConfig.Network.AciNetworkProvider.KafkaClientKeyCluster.Spec.RancherKubernetesEngineConfig.Network.AciNetworkProvider.TokenImportant:
Workarounds
There is no direct mitigation besides updating Rancher to a patched version.
Patches
Patched versions include releases 2.5.17, 2.6.10, 2.7.1 and later versions.
After upgrading to a patched version, it is important to check for the ACISecretsMigrated and RKESecretsMigrated conditions on Clusters and ClusterTemplateRevisions to confirm when secrets have been fully migrated off of those objects, and the objects scoped within them.
For more information
If you have any questions or comments about this advisory:
High Basis: The source's own band: HIGH
2.5.0, fixed 2.5.17 (semver)2.5.17
2.5.17go get github.com/rancher/[email protected]2.6.0, fixed 2.6.10 (semver)2.6.10
2.6.10go get github.com/rancher/[email protected]2.7.0, fixed 2.7.1 (semver)2.7.1
2.7.1go 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