First published: Mon Apr 24 2023(Updated: )
Clusternet is a general-purpose system for controlling Kubernetes clusters across different environments. An issue in clusternet prior to version 0.15.2 can be leveraged to lead to a cluster-level privilege escalation. The clusternet has a deployment called `cluster-hub` inside the `clusternet-system` Kubernetes namespace, which runs on worker nodes randomly. The deployment has a service account called `clusternet-hub`, which has a cluster role called `clusternet:hub` via cluster role binding. The `clusternet:hub` cluster role has `"*" verbs of "*.*"` resources. Thus, if a malicious user can access the worker node which runs the clusternet, they can leverage the service account to do malicious actions to critical system resources. For example, the malicious user can leverage the service account to get ALL secrets in the entire cluster, resulting in cluster-level privilege escalation. Version 0.15.2 contains a fix for this issue.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
GlusterFS | <=0.15.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-30622 has a severity rating that can lead to cluster-level privilege escalation.
To fix CVE-2023-30622, upgrade Clusternet to version 0.15.2 or later.
CVE-2023-30622 affects Clusternet versions before 0.15.2.
CVE-2023-30622 is classified as a privilege escalation vulnerability.
Users and organizations utilizing Clusternet versions prior to 0.15.2 are affected by CVE-2023-30622.