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,758
    • Issues 44,758
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • 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
  • #35102
Closed
Open
Issue created Oct 28, 2019 by yahyaayman@masterhackr

ESCALATED: User must have verified email before enabling 2FA

Description:

1- attacker register with victem email (that not be a user at gitlab)

2- attacker could login without email verification

3- attacker could enable 2FA without email verification

impact: 2fa-enable when user want to register his mail at gitlab and find that some one make an account with his mail he will make a reset password and he will change his password but he cant access the account because 2fa activated by attacker first

Proposal

Don't allow 2FA configuration with an unverified email address.

Edited Sep 09, 2021 by Hannah Sutor
Assignee
Assign to
Time tracking