Trust
https://dockerlabs.es/
🔗 How to setup a Docker Image
Task 1 - Deploy the machine
Install docker.io (if you do not already have it installed) -> sudo apt install docker.io
Download machine from DockerLabs website and setup lab:
unzip trust.zip
sudo bash auto_deploy.sh trust.tar
and we obtained IP machine -> 🎯 Target IP: 172.17.0.2
We can put the IP in the file to associate it with an easier to remember name:
Create a directory for machine on a dedicated folder and subdir containing: nmap,content,exploits,scripts
Task 2 - Reconnaissance and Exploitation
I prefer to start recon by pinging the target, this allows us to check connectivity and get OS info.
Sending these three ICMP packets, we see that the Time To Live (TTL) is ~64 secs. this indicates that the target is a *nix system, while Windows systems usually have a TTL of 128 secs.
2.1 Ports in listening and relative services
Of course, we start looking for information about our target by scanning the open ports with the nmap tool
There're two open port (22, 80), analyze them searching more info about services version and potential vulns:
command | result |
---|---|
sC | run default scripts |
sV | enumerate versions |
A | aggressive mode |
Pn | no ping |
oN | output to file with nmap formatting |
As always we begin our exploration from port 80, where we know there is a web server, so we execute the whatweb command to extract more information and then view the content using the browser
Let's display the default Apache page, try analysing the source page with CTRL+U
But we don't discover nothing of interisting.
2.2 Brute force hidden web directory
Now, we try to find potential hidden directory using gobuster:
We only find a useless 403 status code, so we try inserting web extensions (html, xml and php) with the -x flag:
and finally we obtain two status code 200, the index.html is the homepage (that we just know), therefore we go to the secret.php
We find as info a potential username, remembering that port 22 (SSH) is open, not knowing the password we could try a brute force attack with hydra
2.3 Brute force ssh credentials
Fantastic, we discovered the password, we use it to log in via SSH with the following command: ssh mario@trust
Task 3 - Privilege Escalation
Now that we are inside, since we are not root user we need to elevate our privileges, so let's check the current permissions using sudo -l
We see that mario user has root permissions for /usr/bin/vim, then we can use gtfobins to find it.
using vim sudo command, we obtain a root permission sudo vim -c ':!/bin/sh'
Last updated