forwarded misgivings: the state format behind a header cue

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

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

the feature route invited a forwarded-header request, but the proof depended on state data described by a separate format response.

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 named a feature route and state-format route. the format response supplied a parameter and an encoded json state with a role field.

extraction method

request the current format document, decode its state, change the role using the target's vocabulary, encode it again and submit it under the disclosed parameter. validate the resulting proof.

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 forwarded-header check alone did not produce a proof. following the format document completed the request contract and the same method worked across fresh targets.

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 27 finish: below top 10

  • 0:51.9single#5 of 152 solvers
  • 1:02.6time trial#3 of 148 solvers
  • 1:16.0mastery#3 of 132 solvers
  • #38team day finishof 127 teams that cleared it, in 34:43.1
  • #6single orderof the day's 8, 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 52.9s 1 0 recorded
time trial 10.1s 1 0 recorded
mastery 14.5s 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 126.4s 9.3s 117.1s
mastery 127.3s 13.7s 113.6s

where we got stuck

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

{generated by a clanker}