KubePi: Insufficient per-cluster authorization checks in cluster management APIs
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| 1Panel-dev | KubePi | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| 1panel Dev | Kubepi |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.414% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
1panel Dev
1panel Dev kubepi |
|
| Vendors & Products |
1panel Dev
1panel Dev kubepi |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | KubePi is a Kubernetes multi-cluster management panel. In versions up to and including 2.0.0, cluster-scoped APIs do not consistently validate per-cluster access, allowing an authenticated user with cluster management permissions to operate on clusters outside the scope they were granted. Because the affected endpoints act on cluster-specific data without confirming that the requesting user is authorized for that particular cluster, a user assigned management rights over one cluster can, under certain role and cluster configurations, read or modify data in clusters they should not manage. This issue is fixed in version 2.0.1. | |
| Title | KubePi: Insufficient per-cluster authorization checks in cluster management APIs | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV4_0
|