Calderbank runs a shared helpdesk. Agents are assigned to queues, and a ticket in a queue you are not on is not yours to open.
You are on the hardware queue. Legal, HR and finance run their own queues on the same helpdesk.
The Monday digest email goes to every agent and lists what was uploaded across the whole helpdesk in the past week: file 5512, settlement-countersigned.pdf, on a ticket in the legal queue.
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. Download a file from a ticket in a queue that is not yours.
“Authorising the parent in a nested route authorises everything reached through it.”
Load the child through the parent rather than beside it: fetch the attachment scoped to the ticket you just authorised, so an id belonging to another ticket returns nothing. Where ids are global, check that the child belongs to the parent before serving it. Add a test that asks for a valid attachment id under a ticket it does not belong to and expects a 404.
Anywhere a URL nests one identifier inside another: messages inside threads, invoices inside accounts, documents inside matters, files inside projects, comments inside posts. The tell is that the two identifiers fail differently, one with a permission error and one with a lookup error, which means two different pieces of code are answering for them.
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.