Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,763
    • Issues 44,763
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,330
    • Merge requests 1,330
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #363058
Closed
Open
Issue created May 20, 2022 by Imre Farkas@ifarkas🔴Maintainer

Account take over via SCIM email change

Group administrator with group SSO enabled can take over any user account with known username and email via SCIM provisioning API. 2FA mitigates the impact.

Steps to reproduce:

  1. provision a SCIM user using an existing user's username and email via POST /api/scim/v2/groups/:group_path/Users/ endpoint
  2. update the SCIM provisioned user's email address via PATCH /api/scim/v2/groups/:group_path/Users/:id
  3. confirm email sent to new email

Vulnerability found in https://gitlab.com/gitlab-com/gl-security/security-operations/sirt/operations/-/issues/2270.

Edited May 30, 2022 by Nick Malcolm
Assignee
Assign to
Time tracking