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,761
    • Issues 44,761
    • 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
  • #8180
You need to sign in or sign up before continuing.
Closed
Open
Issue created Oct 29, 2018 by GitLab SecurityBot@gitlab-securitybotReporter

IDOR at /drafts/publish/

HackerOne report #429908 by lucky_sen on 2018-10-28:

Summary: I found IDOR vulnerability at the endpoint /drafts/publish which enable me to publish unauthorised drafts.

Description: There is a feature in discussion where we can save our review as draft and then publish it later. I notice that the ID parameter are not properly check before publish any draft review so i am able to publish any one draft review even there discussion are confidential and i don't have access on it .

Steps To Reproduce:

  1. Make 2 accounts A and B and create separate merge requests in both of them.
  2. Make a draft review in both merge requests by clicking Start a review. Note down B's draft id from the response.
  3. Go through A's account and publish a comment by clicking Add comment now.
  4. Intercept the request and change the Id parameter with B's draft id. (B's draft successfully published)

Supporting Material/References:

  • Screenshot_2018-10-28_15_13_21.png
  • Screenshot_2018-10-28_15_13_36.png
  • Screenshot_2018-10-28_15_13_49.png

Impact

Attacker are able to publish some one confidential draft with out any authentication.

Thanks!

Attachments

Warning: Attachments received through HackerOne, please exercise caution!

  • Screenshot_2018-10-28_15_13_49.png
  • Screenshot_2018-10-28_15_13_36.png
  • Screenshot_2018-10-28_15_13_21.png
Edited Oct 29, 2018 by Dennis Appelt
Assignee
Assign to
Time tracking