BigW Consortium Gitlab

  1. 10 Feb, 2017 1 commit
  2. 16 Dec, 2016 4 commits
  3. 26 Nov, 2016 1 commit
  4. 11 Nov, 2016 1 commit
  5. 13 Sep, 2016 1 commit
  6. 20 Jul, 2016 2 commits
  7. 05 Jul, 2016 1 commit
  8. 01 Jul, 2016 2 commits
  9. 24 Jun, 2016 1 commit
    • Fix an information disclosure when requesting access to a group containing private projects · aec3475d
      Rémy Coutable authored
      The issue was with the `User#groups` and `User#projects` associations
      which goes through the `User#group_members` and `User#project_members`.
      
      Initially I chose to use a secure approach by storing the requester's
      user ID in `Member#created_by_id` instead of `Member#user_id` because I
      was aware that there was a security risk since I didn't know the
      codebase well enough.
      
      Then during the review, we decided to change that and directly store the
      requester's user ID into `Member#user_id` (for the sake of simplifying
      the code I believe), meaning that every `group_members` / `project_members`
      association would include the requesters by default...
      
      My bad for not checking that all the `group_members` / `project_members`
      associations and the ones that go through them (e.g. `Group#users` and
      `Project#users`) were made safe with the `where(requested_at: nil)` /
      `where(members: { requested_at: nil })` scopes.
      
      Now they are all secure.
      Signed-off-by: 's avatarRémy Coutable <remy@rymai.me>
  10. 20 Jun, 2016 2 commits
  11. 18 Jun, 2016 1 commit
  12. 16 Jun, 2016 2 commits
  13. 14 Jun, 2016 2 commits