pass the identity: the photocopied hall pass
huntress ctf 2026, day 30 · web exploitation · three modes
tools used: live web target capture, saved web inspection, and timed-attempt pipeline.
the target presented itself as an axum-based delegated access desk. its clue document named a feature route, a secondary result route and an identity directory. both routes rejected the signed-in analyst, and every rejection carried a vary header naming the field the server actually keyed on — one nobody was sending.
challenge shape
single and time trial each assigned one temporary target and one answer. mastery assigned multiple targets and answer ids. each assignment rotated the feature route, the result route and the host. the answer for each target was the proof string the target itself returns once the right identity crosses the delegated boundary.
artifact anatomy
the useful artifact was the saved sequence of http responses. the home page linked to a clue document. the clue named the current feature route, the secondary result route and an identity directory route, together with the caller's current role. a plain get of either the feature or the result route answered 403 with delegated_identity_rejected, and both denials carried vary: x-delegated-user. the identity directory answered 200 with the caller's own name and a records owner that did not belong to the caller.
extraction method
we read the directory first. the feature and result routes authorize a delegated identity from a request header, and the vary header named it. the records owner the directory disclosed is an identity the target itself trusts for exactly these routes. requesting either route with X-Delegated-User: <records owner> carries that identity across the delegated boundary — a photocopied hall pass — and the target returns the proof.
validation and answer formatting
each target's proof appears only in that target's response. nothing carries between assignments: the routes, the directory contents and the proof all rotate with the host.
failed approaches and pivots
the standard forwarding-header sweep (forwarded-for, real-ip and friends) returned the same 403 every time, because the server never keyed on a forwarding header. spoofing the caller's own role also changed nothing. the identity directory was the tell: it disclosed an identity that exists solely to be delegated to.
automation across modes
the shared collector now follows the identity directory, ranks the disclosed identities with the owner-keyed ones first, and sweeps them under the observed header name and its alternates on both routes. a renamed variant of this class resolves in the first capture, before any racer session opens.
lessons
- a vary header names the exact input a response caches on; when a denial varies on a header nobody sent, that header is the whole challenge.
- an access-control boundary that trusts a caller-supplied identity header is only as strong as the directory that decides which identities exist.
- the identity that does not belong to you is the one the target expects you to present; read who the records belong to before arguing with the door.
solve times
public scoreboard · day 30 finish: below top 10
- 0:53.7single#4 of 136 solvers
- 1:01.5time trial#2 of 131 solvers
- 1:13.9mastery#2 of 117 solvers
- #14team day finishof 52 teams that cleared it, in 2h43m
- #4single orderof the day's 7, by our flag time
from the public scoreboard: 09:00 et release to our flag; the table below counts from our attempt's start.
the table measures from the first local work on the mode to recorded team completion.
| mode | work to flag | local attempts | wrong submits |
|---|---|---|---|
| single | about 41s | 1 | 0 |
| time trial | about 7s | 1 | 0 |
| mastery | about 10s | 1 | 0 |
the clock
the winning timed attempts' assignment deadlines were not preserved in the local record.
| mode | time available | time used | time left |
|---|---|---|---|
| time trial | not recorded | not recorded | not recorded |
| mastery | not recorded | not recorded | not recorded |
where we got stuck
- the first capture spent its sweep on forwarding headers the target ignored; the vary header naming
x-delegated-userwas in the saved response the whole time. - the single went to a racer session that read the directory and wrote the header recipe in one edit; the class is deterministic since the after-action, so the same shape will not need one again.
flags: single, time trial, and mastery [redacted].