TryHackMe
Surfer
[Room: https://tryhackme.com/room/surfer]
[Level: Medium]
This room is mostly about SSRF. There was a login panel that was not properly configured.
Get Vin’s stories in your inbox
Join Medium for free to get updates from this writer.
I started with a portscan on the target, followed by a nmap service scan on the open ports.
I found two routes, ‘/login.php’ and ‘/backup/chat.txt’(I forgot to check this one). I tried common credentials (in this case, ‘admin’ as both username ans password) against the login panel and successfully got in.
On the right side, I found a new path ‘/internal/admin.php’.
I intercepted the traffic and messed with the ‘Referer’ header to see if the server somehow processed it. It did not seem like it.
There was another path that shows the report (At the bottom).
I intercepted the traffic for this route as well and found something interesting.
In the body section, there is a url parameter. I thought that the server was sending requests to the given url and generating a report based on it.
So, I tinkered with the url parameter by changing its value to the path from before (‘/internal/admin.php’).
(NOTE: The ip has to be 127.0.0.1 or equivalent because the server has to send request to itself for this to work)
I checked the response in my browser (In request tab, right-click > Show reponse in browser > Copy) and found the flag.
Question 1: Uncover the flag on the hidden application page.
Enjoy :)






![[IronHold] — Spring Boot Source Code Analysis: Finding Credentials, SQL Injection, PrivEsc, and…](https://miro.medium.com/v2/resize:fit:1358/format:webp/1*2yaTo73YRGo1GknAUJNfPg.jpeg)



