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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| yeti-platform | yeti | ≤ 2.11.0 | — |
References
- GitHub Issue #1349 issue-tracking
- https://github.com/yeti-platform/yeti product
- the delete handler performs no permission check technical-description
- sibling handlers require Role.OWNER technical-description
- VulnCheck Advisory: Yeti through 2.11.0 Missing Authorization on RBAC Relationship Deletion third-party-advisory