Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #5185

Closed
Open
Created Sep 26, 2013 by Administrator@rootOwner

[6.1] Bug with Merge Requests

Created by: crazyscience

Summary: Basically, you can get into a situation where the Merge Request page shows a diff that's one thing, but upon approval, the merge request could be something completely different, and possibly malicious.

How to reproduce: -Create a project w/some commits -Fork the project -Make a commit on the forked repo -Submit a merge request requesting to merge this new commit into the original repo This will be the diff displayed on the merge request page -Make another commit on the forked repo This will be the commit that is actually going to be merged into the original -Notice that the merge request page does not show this new commit -Approve the merge request -Gasp in horror as unapproved code is merged into the project

Assignee
Assign to
Time tracking