Browse Source
A Custom member with only the manage_groups permission could revoke other members' collection access via two endpoints that were missing the collection-access check enforced elsewhere (put_group_members, edit_member): - POST /organizations/<org>/groups/<group>/delete-user/<member> (post_delete_group_member) removed a member from any group, including collection-bearing ones. - DELETE /organizations/<org>/groups/<group> and its bulk variant (delete_group_impl / bulk_delete_groups) deleted collection-bearing groups outright, revoking access for all their members. Neither path can grant access, so confidentiality was never at risk, but both let a manage_groups-only user tamper with other members' collection access, contradicting the permission's invariant. Both now require Admin/Owner or full collection access before touching a group that confers collection access (via access_all or assigned collections).pull/7397/head
1 changed files with 31 additions and 0 deletions
Loading…
Reference in new issue