01-26-2025, 10:20 PM
1. use tools like nmap to scan for open ports on the gitLab instance look for port 80/443 for web 22 for SSH.
2. find a vulnerability maybe it's an outdated gitLab version with known cves or a weak admin password.
3. once you're in look for the CI/CD configuration files. They're usually in .gitlab-ci.yml in project repos.
4. modify the YAML files add commands to the build process maybe a backdoor or some data exfiltration.
5. force a new build to run your injected code.
6. delete the logs bro for the sake of your mother.
2. find a vulnerability maybe it's an outdated gitLab version with known cves or a weak admin password.
3. once you're in look for the CI/CD configuration files. They're usually in .gitlab-ci.yml in project repos.
4. modify the YAML files add commands to the build process maybe a backdoor or some data exfiltration.
5. force a new build to run your injected code.
6. delete the logs bro for the sake of your mother.