Security lab
DNS Rebinding
The application trusts a hostname as a safe origin even after that hostname has been rebound to an internal IP, allowing an attacker to pivot from a public host to an internal service and read sensitive data.
Lab objective
Probe the trusted host and exploit the rebinding gap to fetch internal content that should never be reachable from the browser and recover the hidden token.
Tools you will use
- browser
- Burp Suite
- curl
What this lab teaches
Network labs cover reconnaissance, service enumeration, and protocol abuse inside an isolated segment. You map a small target network, identify exposed services, and practise the exploitation and pivoting techniques used during internal assessments — all scoped to the sandbox so no real host is ever touched.
Hints & approach
- 01The app fetches a target URL from the client and does not differentiate between the hostname and the resolved IP address.
- 02A public host can later point to a private or loopback target after a DNS rebinding attack.
- 03Examine whether an internal-looking URL is accepted when it should not be.
How the sandbox works
When you start the lab, Vulnarex provisions an isolated, per-user environment and opens it in a new tab. Each session has its own target and state, so nothing you do here can affect another learner or any external system. You can reset the environment at any time and re-approach the challenge from a clean slate.