TryHackMe - Corridor Walkthrough
A walkthrough of the TryHackMe Corridor room, exploring IDOR vulnerabilities and MD5 hashing.
You have found yourself in a strange corridor. Can you find your way back to where you came?
In this challenge, you will explore potential IDOR vulnerabilities. Examine the URL endpoints you access as you navigate the website and note the hexadecimal values you find (they look an awful lot like a hash, don’t they?). This could help you uncover website locations you were not expected to access.
Access TryHackMe lab here: Corridor
Reconnaissance
Always start with scanning and playing around the web page to find all the entry points and get as information as possible. For this room, I started with nmap scan to find open ports and services running on the target machine.
Nmap Scan
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
root@ip-10-48-136-92:~# nmap -p- 10.48.177.244
Starting Nmap 7.80 ( https://nmap.org ) at 2026-05-11 05:33 BST
mass_dns: warning: Unable to open /etc/resolv.conf. Try using --system-dns or specify valid servers with --dns-servers
mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-servers
Nmap scan report for 10.48.177.244
Host is up (0.00015s latency).
Not shown: 65534 closed ports
PORT STATE SERVICE
80/tcp open http
MAC Address: 02:54:82:AB:18:21 (Unknown)
Nmap done: 1 IP address (1 host up) scanned in 2.21 seconds
Open port: 80 (HTTP)
Nmap scan revealed that port 80 is open, indicating “http” service is running.
Enumeration
After loading “http://IP_address/” in the browser, we land on Home page.
There are 13 doors in the Corridor (Web page) and each leads to different pages/ destinations. Click on any of the doors and observe the hash in the URL. Each door gives different hash value. All the URLs are given below.
1
2
3
4
5
6
7
8
9
10
11
12
13
http://10.48.177.244/c4ca4238a0b923820dcc509a6f75849b
http://10.48.177.244/c81e728d9d4c2f636f067f89cc14862c
http://10.48.177.244/eccbc87e4b5ce2fe28308fd9f2a7baf3
http://10.48.177.244/a87ff679a2f3e71d9181a67b7542122c
http://10.48.177.244/e4da3b7fbbce2345d7772b0674a318d5
http://10.48.177.244/1679091c5a880faf6fb5e6087eb1b2dc
http://10.48.177.244/8f14e45fceea167a5a36dedd4bea2543
http://10.48.177.244/c9f0f895fb98ab9159f51fd0297e236d
http://10.48.177.244/45c48cce2e2d7fbdea1afc51c7c6ad26
http://10.48.177.244/d3d9446802a44259755d38e6d163e820
http://10.48.177.244/6512bd43d9caa6e02c990b0a82652dca
http://10.48.177.244/c20ad4d76fe97759aa27a0c99bff6710
http://10.48.177.244/c51ce410c124a10e0db5e4b97fc2af39
Each string contains 32 hexadecimal characters, which strongly resembles md5 hash. Now, the task is to find the value of tha hash. I used this tool to find original values of the hashes.
After computing the hashes, I found that each hash represents a number. Numbers from 1 through 13. Now I know that adding the hash value of a number after “http://IP_address/” in the URL gives me a hint to find the flag. Then I considered trying the values outside of these numbers range. Hashes of next consecutive numbers 14, 15 and 16 returned invalid pages but trying out the hash of ‘0’ which is cfcd208495d565ef66e7dff9f98764dareturned the flag.
Submit the flag to complete the room.
Conclusion
This room demonstrated how predictable object identifiers and insufficient authorization checks can lead to IDOR vulnerabilities. It also tells us the importance of knowledge on common hash formats such as MD5, SHA, etc I fied is crucial.
Lessons Learned
Learned how IDOR (Insecure Direct Object Reference) vulnerabilities can expose unauthorized resources through predictable object identifiers.
Learned how MD5 hashing works and how weak hashes can be identified or cracked using online databases and wordlists.
Learned the importance of validating user authorization on the server side instead of relying solely on client-controlled identifiers.


