GitLab
Gitlab exploitation
Footprinting & Discovery
http://gitlab.inlanefreight.local:8081/users/sign_in

The only way to footprint the GitLab version number in use is by browsing to the /help page when logged in
Enumeration
Browse to /explore and see if there are any public projects that may contain something interesting.
Check and see if we can register an account and access additional projects
User Enumeration
http://gitlab.inlanefreight.local:8081/users/sign_up

GitLab's defaults are set to 10 failed attempts resulting in an automatic unlock after 10 minutes

Authenticated Remote Code Execution
GitLab Community Edition version 13.10.2 and lower suffered from an authenticated remote code execution
If we encounter a vulnerable version of GitLab that allows for self-registration, we can quickly sign up for an account and pull off the attack. Else, OSINT or password guessing
Gitlab 14.9 CVE-2022-1162
New Gitlab Accounts (created since the first affect version and if Gitlab is before the patched version) can be logged into with the following password:
123qweQWE!@#000000000
Source: https://x.com/HackerGautam/status/1520624546654867456
CVE-2023-7028 - Admin Account Take Over
Account-Take-Over vulnerability that allows users to take control of the gitlab administrator account without user interaction
GitLab Authentication Bypass (CVE-2024-45409)
All the following GitLab (CE/EE) versions are vulnerable:
< 16.11.10
17.0.0 < 17.0.8
17.0.0 < 17.1.8
17.0.0 < 17.2.7
17.0.0 < 17.3.3
Resources
Interesting Books
Interesting BooksThe Web Application Hacker’s Handbook The go-to manual for web app pentesters. Covers XSS, SQLi, logic flaws, and more
Bug Bounty Bootcamp: The Guide to Finding and Reporting Web Vulnerabilities Learn how to perform reconnaissance on a target, how to identify vulnerabilities, and how to exploit them
Real-World Bug Hunting: A Field Guide to Web Hacking Learn about the most common types of bugs like cross-site scripting, insecure direct object references, and server-side request forgery.
Last updated