Ashgrove builds hosted status pages. It can import an existing feed by URL, and it runs on EC2.
You control notes.example. Its /feed route is a test endpoint, so you can choose its HTTP status, headers, and body.
One change to this request triggers the vulnerability. The challenge is to use your security intuition to work out what to change. Find the value the server shouldn’t trust, change it, and send it. The response tells you whether you were right.
Hint. Make the importer fetch an address its validation blocks.
“Validating the first URL is enough, even when the HTTP client follows redirects.”
Disable redirects for user-supplied URLs. If redirects are required, resolve and validate every hop, reject private and reserved addresses, and connect only to the IP that passed validation. Do not return fetched bodies in errors. Require IMDSv2, use a least-privileged AWS role, and add tests for redirects and DNS rebinding.
Check feed imports, webhook tests, link previews, remote images, PDF renderers, and document converters. Look for a server-side HTTP client that accepts user-controlled URLs, follows redirects, or returns fetched content in errors.
One Request Away is a daily series of challenges. They’re like code review, but for HTTP requests: in each one you’re one request away from triggering a vulnerability, and your goal is to identify what you need to change.