Skip to content

A potential risk in clusternet which can be leveraged to make a cluster-level privilege escalation

Moderate severity GitHub Reviewed Published Apr 21, 2023 in clusternet/clusternet • Updated Nov 9, 2023

Package

gomod github.com/clusternet/clusternet (Go)

Affected versions

< 0.15.2

Patched versions

0.15.2

Description

Summary:

A potential risk in clusternet which can be leveraged to make a cluster-level privilege escalation.

Detailed analysis:

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, he/she can leverage the service account to do malicious actions to critical system resources. For example, he/she can leverage the service account to get ALL secrets in the entire cluster, resulting in cluster-level privilege escalation.

References

@dixudx dixudx published to clusternet/clusternet Apr 21, 2023
Published to the GitHub Advisory Database Apr 21, 2023
Reviewed Apr 21, 2023
Published by the National Vulnerability Database Apr 24, 2023
Last updated Nov 9, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L

EPSS score

0.044%
(14th percentile)

Weaknesses

CVE ID

CVE-2023-30622

GHSA ID

GHSA-833c-xh79-p429

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.