Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
W
WebComplete_Skeleton
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Hi Sir, mv-data.at Team Introduce, I'm Alexander. I work as Bug Bounty Hunter. I found a vulnerability in an existing Gitlab system Gitlab RCE which allows me to change the gitlab administrator/root password (Takeover admin gitlab login) and also be able to view all source code and secret credentials make reverse shell to the operation system. This finding is Critical Vulnerability. Impact:

Attacker can delete and download the source code and obtain various credentials. (database[SQL Command], API, credential : username & password) Attacker can embed ransomware and demand a ransom for all your data Can distribute the existing code in gitlab or sell it causing damage to the reputation Can exploit the gitlab and all source code of your data dev or master RCE Access can delete and manage your files or data. Email: alexandergiat@gmail.com
  • Vojislav Vukovic
  • WebComplete_Skeleton
  • Issues
  • #3

Closed
Open
Opened Jan 04, 2019 by Dominik Schiener@schiener

ID's must be backend generated

  • The IDs of the SeatingPlanPage and the SeatingPlan Page MUST NOT be generated in the frontend, due to the possibility that an ID is generated twice
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: Vojislav/WebComplete_Skeleton#3