Cowley Wells uses a central portal to connect staff accounts to third-party tools. A reporting tool has prepared this consent link for its users.
You are reviewing the link before it is shared with staff. You also control notes.example.
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. Send the browser that follows this link to a host you control.
“A value that begins with a slash is a path on this site.”
Resolve the destination with a URL parser and allow it only when the final scheme and host match your own origin. A safer design is to accept a short destination name and look up its path on the server. Add tests for values beginning with two slashes, encoded slashes, and backslashes.
Check login, consent, logout, password reset, and invitation flows. Look for parameters such as return_to, next, continue, redirect_uri, and RelayState, especially when the code validates them with a prefix or regular expression.
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.