Learn / SSRF
Trick a server into leaking its own secrets
SSRF (Server-Side Request Forgery) happens when a server fetches a URL you provide — which lets an attacker make requests from inside the network.
You send a request
You ask the application to get a URL for you, for example:
GET https://openvaultbank.example/preview?url=https://images.example/cat.jpgThis request goes to the proxy (the front door).
Passed to the app server
The proxy forwards the request to the app server inside the private network.
The server fetches the URL
The app server makes a request to the URL you gave it, using its own network access. Here it fetches the image from an image container, and the picture comes back out to you.
Because this request is made from inside the network, it can also reach other internal services — databases, admin panels, and more.
Now you try
Change the address the app is asked to fetch and see what comes back. Everything here is pretend.
Try 169.254.169.254, 10.0.0.5 or /admin
You found the one nobody mentions. Nothing here but a cat in sunglasses.
This is one bug, on one pretend app. A real test goes through everything you’ve built, feature by feature, and hands you a plain report: what we found, how bad it is, and exactly what to change. See how we test internet-facing apps →
Curious what we'd find in yours?
Tell us what you've built and you'll have a quote after a short call.