CVE-2024-22032: Rancher's RKE1 Encryption Config kept in plain-text within cluster AppliedSpec
Impact This issue is only relevant to clusters provisioned using RKE1 with secrets encryption configuration enabled. A vulnerability has been identified in which an RKE1 cluster keeps constantly reconciling when secrets encryption configuration is enabled (please see the RKE documentation). When reconciling, the Kube API secret values are written in plaintext on the AppliedSpec.
Published Jun 17, 2024 · Updated Oct 16, 2024
Affected packages
github.com/rancher/rancher
- Ecosystem
- Go
- Affected
- >= 2.7.0, < 2.7.14
- Fixed in
- 2.7.14
- Check
go list -m github.com/rancher/rancher
github.com/rancher/rancher
- Ecosystem
- Go
- Affected
- >= 2.8.0, < 2.8.5
- Fixed in
- 2.8.5
- Check
go list -m github.com/rancher/rancher
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
This issue is only relevant to clusters provisioned using RKE1 with secrets encryption configuration enabled.
A vulnerability has been identified in which an RKE1 cluster keeps constantly reconciling when secrets encryption configuration is enabled (please see the RKE documentation). When reconciling, the Kube API secret values are written in plaintext on the AppliedSpec. Cluster owners, Cluster members, and Project members (for projects within the cluster), all have RBAC permissions to view the cluster object from the apiserver.
This could lead to an unauthorized user gaining access to the entire secrets encryption config specific for the cluster, only on the applied spec.
Since this affects only custom encryption configurations, users need to manually rotate the keys by editing the cluster. For more information, please refer to the RKE secrets encryption documentation.
The full custom configuration example:
services:
kube-api:
secrets_encryption_config:
enabled: true
custom_config:
apiVersion: apiserver.config.k8s.io/v1
kind: EncryptionConfiguration
resources:
- resources:
- secrets
providers:
- aescbc:
keys:
- name: k-fw5hn
secret: RTczRjFDODMwQzAyMDVBREU4NDJBMUZFNDhCNzM5N0I= #<--- needs to be changed
- identity: {}Please consult the associated MITRE ATT&CK - Technique - Unsecured Credentials for further information about this category of attack.
Patches
To address this issue, the fix introduces a new change that copies the AppliedSpec before mutating. As such, the next time the cluster is reconciled and the AppliedSpec is set, all references to sensitive data will be removed.
Patched versions include releases 2.7.14 and 2.8.5.
Workarounds
There are no workarounds for this issue. Users are recommended to upgrade, as soon as possible, to a version of RKE/Rancher Manager which contains the fixes.
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.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-41052
Rancher has Privilege Escalation from Project Owner to Host
critical8.4Jul 1, 2026CVE-2026-41053
Rancher has over-inclusive team membership expansion in GitHub App authentication provider
high8.8Jul 1, 2026CVE-2026-44939
Rancher vulnerable to command injection through unsanitized YAML parameter
critical9.6Jul 1, 2026CVE-2026-25705
Rancher Extensions have arbitrary file access via path traversal
high8.4May 7, 2026CVE-2021-25320
Rancher cloud credentials can be used through proxy API by users without access
critical9.9Mar 3, 2026CVE-2021-36783
Rancher doesn't properly sanitize credentials in cluster template answers
critical9.9Mar 3, 2026
