serialized offender: a role inside encoded state

huntress ctf 2026, day 26 · web exploitation · all three modes

tools used: live web target capture, saved web inspection, and timed-attempt pipeline.

the target accepted a state parameter whose format document carried an encoded json example. the role was read from the object and changed within the target's current vocabulary.

challenge shape

single and time trial assigned one target each. mastery assigned multiple independently captured targets, which could mix web families. each proof belonged to its own target.

artifact anatomy

the clue response named the feature and state-format routes. the format response identified the parameter and supplied encoded state. the feature response separated invalid state from a proof-bearing accepted request.

extraction method

read the current format response, decode its state object, change the role field using a role named by that response, re-encode the object, and submit it under the disclosed parameter. validate one proof in the response.

validation and answer formatting

every route must remain on the assigned origin. current target values are read again in each mode, and a successful status alone is insufficient. a proof is submitted only when the response contains it. submitted results are [redacted].

failed approaches and pivots

the delay was in the live worker's edit path; the deterministic recipe submitted the single and then both timed modes without a wrong answer.

automation across modes

the collector classifies every target independently and keeps each proof paired with its answer id. the same evidence order is applied to each fresh time-trial or mastery target.

lessons

solve times

public scoreboard · day 26 finish: below top 10

  • 4:37.0single#50 of 156 solvers
  • 4:47.0time trial#38 of 152 solvers
  • 4:56.8mastery#20 of 147 solvers
  • #32team day finishof 135 teams that cleared it, in 19:21.9
  • #6single 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 recorded work began with the assigned target. external completions and missing local winning captures are marked as such.

mode work to flag attempts wrong submits
single 4m37.7s 1 0 recorded
time trial 9.8s 1 0 recorded
mastery 10.8s 1 0 recorded

the clock

the winning assignments recorded start and deadline. time used is the assignment start to the recorded flag, rounded to a tenth of a second.

mode time available time used time left
time trial 125.4s 9.2s 116.1s
mastery 125.6s 10.0s 115.5s

where we got stuck

flags: single, time trial, and mastery [redacted].

{generated by a clanker}