9.9 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
6.5 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
SINGLE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:N/AC:L/Au:S/C:P/I:P/A:P
0.041 Low
EPSS
Percentile
92.0%
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.clustertemplaterevisions
The 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[].Secret
Cluster.Spec.RancherKubernetesEngineConfig.Services.KubeAPI.SecretsEncryptionConfig.CustomConfig.Providers[].AESCBC.Keys[].Secret
Cluster.Spec.RancherKubernetesEngineConfig.Services.KubeAPI.SecretsEncryptionConfig.CustomConfig.Providers[].SecretboxConfiguration.Keys[].Secret
Cluster.Spec.RancherKubernetesEngineConfig.Services.Kubelet.ExtraEnv
when containing the AWS_SECRET_ACCESS_KEY
environment variableCluster.Spec.RancherKubernetesEngineConfig.BastionHost.SSHKey
Cluster.Spec.RancherKubernetesEngineConfig.PrivateRegistries[].ECRCredentialPlugin.AwsSecretAccessKey
Cluster.Spec.RancherKubernetesEngineConfig.PrivateRegistries[].ECRCredentialPlugin.AwsSessionToken
Cluster.Spec.RancherKubernetesEngineConfig.Network.AciNetworkProvider.ApicUserKey
Cluster.Spec.RancherKubernetesEngineConfig.Network.AciNetworkProvider.KafkaClientKey
Cluster.Spec.RancherKubernetesEngineConfig.Network.AciNetworkProvider.Token
Important:
For the exposure of credentials not related to Rancher, the final impact severity for confidentiality, integrity and availability is dependent on the permissions the leaked credentials have on their services.
It is recommended to review for potentially leaked credentials in this scenario and to change them if deemed necessary.
There is no direct mitigation besides updating Rancher to a patched version.
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.
If you have any questions or comments about this advisory:
9.9 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
CHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
6.5 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
SINGLE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:N/AC:L/Au:S/C:P/I:P/A:P
0.041 Low
EPSS
Percentile
92.0%