CVE-2023-22647: Rancher vulnerable to Privilege Escalation via manipulation of Secrets
(updated )
A vulnerability has been identified which enables Standard users or above to elevate their permissions to Administrator in the local
cluster.
The local
cluster means the cluster where Rancher is installed. It is named local
inside the list of clusters in the Rancher UI.
Standard users could leverage their existing permissions to manipulate Kubernetes secrets in the local
cluster, resulting in the secret being deleted, but their read-level permissions to the secret being preserved. When this operation was followed-up by other specially crafted commands, it could result in the user gaining access to tokens belonging to service accounts in the local
cluster.
Users that have custom global roles which grant create
and delete
permissions on secrets
would also be able to exploit this vulnerability.
Users with audit logs enabled in Rancher can try to identify possible abuses of this issue by going through the logs. To sieve through the data filter by kind: Secret
with type: provisioning.cattle.io/cloud-credential
, then investigate all log entries that affect that specific resource. A secondary check would be to filter by all operations with Opaque
Secrets within the cattle-global-data
namespace.
After patching, it is recommended that users review access methods to Rancher (including RBAC policies, tokens, and host-level node access), to ensure that no changes were made to persist access to users who have leveraged this vulnerability.
References
- bugzilla.suse.com/show_bug.cgi?id=CVE-2023-22647
- github.com/advisories/GHSA-p976-h52c-26p6
- github.com/rancher/rancher
- github.com/rancher/rancher/releases/tag/v2.6.13
- github.com/rancher/rancher/releases/tag/v2.7.4
- github.com/rancher/rancher/security/advisories/GHSA-p976-h52c-26p6
- nvd.nist.gov/vuln/detail/CVE-2023-22647
Detect and mitigate CVE-2023-22647 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →