Add Scenario - Git Dejavu #361
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addition of a new scenario as requested.
Scenario contains an instance of gitlab ce version 13.10.2 on the web server. A flag is pre leaked in robots.txt. This version is vulnerable to CVE-2021-22205 which can be exploited to get a shell as the git user. Upon exploiting and getting a shell, the user can traverse to /home/git and there is a hidden .credentials file containing a login for the gitlab site. Upon doing so they will see a repository titled dev_notes. A flag can then be found in the previous commit. The server also contains an apt get priv esc vulnerability in order to find the final flag in the root directory.
In future it could be amended to allow for a port to be passed as a parameter, but during my testing it threw an error 502 so I kept it as default of 80. There is also potential for the files on the gitlab repo to be more personalised, for example if an organisation is passed in it could contain specific names or information.