Server-Side Request Forgery
See how server-side fetches can be abused to reach internal resources, and how allow-lists and egress control prevent it.
Scenario
The sandbox has a feature that fetches a URL on the server's behalf. It doesn't restrict the destination, so it can be pointed at internal resources it shouldn't reach.
Objective
Reach the internal marker endpoint through the sandbox's fetch feature, then design the controls that prevent SSRF.
Your approach
- Find the feature that performs a server-side fetch.
- Confirm the destination is user-controllable.
- Reach the designated internal marker endpoint to prove impact.
- Map what else the server could reach in a real environment (internal services, metadata).
- Design destination allow-listing and network egress controls.
Rules of engagement
Run this lab only in the isolated environment provided — the downloadable bundle runs on your own machine in a private Docker network. Only interact with the lab's target, keep testing non-destructive, and never use these techniques on systems you don't own or aren't authorised to test. When you've met the objective, submit the flag (format SS{...}) to score.
Remediation focus
Validate destinations against a strict allow-list, resolve and verify targets, block internal ranges and cloud metadata endpoints, and segment egress at the network layer.
Deliverable
Write up what you did, what you observed, the business impact, and a clear remediation — exactly as you would in a professional report.
Hints
Hint 1
Re-read the matching knowledge-base entry before you start.
Hint 2
Capture reproducible evidence as you go — you'll need it for the write-up.
Hint 3
For every finding, identify the single control that would prevent it.
Study the theory
Read the Server-Side Request Forgery (SSRF) knowledge-base entry