Yeti through 2.11.0 Missing Authorization on RBAC Relationship Deletion
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| yeti-platform | yeti | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Yeti-platform | Yeti |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.504% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Yeti through 2.11.0 fails to validate caller permissions in the DELETE /api/v2/rbac/{id} endpoint, allowing users with read access to delete access control relationships. Attackers can revoke the owner's grant and permanently lock legitimate owners out of objects. | |
| Title | Yeti through 2.11.0 Missing Authorization on RBAC Relationship Deletion | |
| First Time appeared |
Yeti-platform
Yeti-platform yeti |
|
| Weaknesses | CWE-862 | |
| CPEs | cpe:2.3:a:yeti-platform:yeti:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Yeti-platform
Yeti-platform yeti |
|
| References |
|
|
| Metrics |
cvssV3_1
|