Thornleigh is an applicant tracking system used by recruitment agencies. Each recruiter works their own requisitions, and the pipeline screen shows what is theirs.
Agencies on Thornleigh compete with each other. A recruiter at one agency should not be able to see candidates at another.
This is the request the pipeline screen makes when it loads.
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. Read applications that are not on your requisitions.
“The list is scoped because the screen that requests it always asks for the right scope.”
Scope the query on the server from the authenticated session, not from a parameter, so that the owner clause is present whether or not the client sends one. Treat filters as narrowing a set the caller is already entitled to, and add a test that requests the collection with no filters at all and expects only the caller's own rows.
Anywhere the front end sends the scope it wants: owner=me, mine=true, tenant ids in a query string, an organisation filter on a report, a customer parameter on a search. The tell is a parameter whose value is always the same, and the check is to remove it rather than change it, because a filter that is absent is simply not applied.
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.