Rancher users who can create Projects can gain access to arbitrary projects
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| SUSE | rancher | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Suse | Rancher |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-8h6m-wv39-239m | Rancher users who can create Projects can gain access to arbitrary projects |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.435% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Suse
Suse rancher |
|
| Vendors & Products |
Suse
Suse rancher |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A vulnerability has been identified within Rancher where a user with the ability to create a project, on a certain cluster, can create a project with the same name as an existing project in a different cluster. This results in the user gaining access to the other project in the different cluster, resulting in a privilege escalation. This happens because the namespace used on the local cluster to store related resources (PRTBs and secrets) is the name of the project. | |
| Title | Rancher users who can create Projects can gain access to arbitrary projects | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|