One Request Away No. 16 Streak 0 Solved 0 of 27

The file that outlived its ticket

Easy IDOR 25 Aug 2026 Solved by 5

Scenario

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.

Request Tap any part of it
//// HTTP/1.1
Host:
Accept:
Cookie: helpdesk_session=
No change — send it as it stands
Response

  • 01 What the server believed

    “Authorising the parent in a nested route authorises everything reached through it.”

  • 02 The fix

    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.

  • 03 Where else to look for this

    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.

The series

Every drill 27

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.

Do not stop here

A drill is one request.
A lab is the whole app.

Uphack labs are believable products with one realistic flaw buried in an ordinary feature. Same instinct, nothing highlighted — you get a running application and have to find it yourself.

Browse the labs
Registration is open Closes today

Turn the instinct into practice.

Drills are free and stay that way. The labs put the same reasoning against a whole application, and members get all of them. Registration is open until Saturday 19 September.

Create your account

Already a member? Sign in