internal affairs: an id inside the fetch

huntress ctf 2026, day 29 · web exploitation · three modes

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

the target presented itself as a ktor-based case intake. its clue response named a feature route, a case directory route and a topology route, plus the current role and a service pattern in plain words: a server-side case fetch. the topology answered a concrete internal case service on loopback, and the directory listed cases with owners. the feature route fetched whatever url it was handed, so the trick was composing the target it fetched.

challenge shape

single and time trial each assigned one temporary target and one answer. mastery assigned five targets and five answer ids. each assignment rotated the feature route and the host. the answer for each target was the proof string the internal service returns when the fetched case belongs to another role.

artifact anatomy

the useful artifact was the saved sequence of http responses. the clue named the feature route, the topology route and the case directory route, and the current role. the topology response named an absolute internal case service url on loopback. the directory response listed cases with ids and owners, including one owned by a role other than the current one. a plain get of the feature route answered with a bad-request error that named its own query parameter.

extraction method

we read the topology and the directory first. the loopback service is only reachable from the target itself, so the id has to live inside the url the feature route fetches. composing the internal service url with the cross-role case id appended as its own query returns that case, with the proof attached.

topology = get(topology_route)
directory = get(directory_route)
victim = next(c["id"] for c in directory["cases"]
              if c["owner"] != current_role)
target = f'{topology["case_service"]}?id={victim}'
proof = get(feature_route, params={"target": target})["evidence"]

the internal service url and the case ids are omitted here. they rotate with each assignment; both come from the current target's own topology and directory responses.

validation and answer formatting

the flow runs only when the current clues name all three routes and the current role. every request the solver sends stays on the assigned origin; the composed url is only ever a value the feature route fetches server-side. a not-found response means the fetch did not resolve a case of another role, and a bad-request response means the parameter was absent. the proof had to appear in this target's response before it was submitted for that target's answer id.

failed approaches and pivots

fetching the cross-role case id through the public directory path did not resolve it; the case service is a separate internal boundary. placing the id beside the target instead of inside it failed the same way, because the fetch must resolve on the loopback service. only the composed url, with the id inside the fetched target, returned the case.

automation across modes

the same topology-derived service url and directory-derived id apply to fresh time-trial and mastery targets. the routes and both values rotate with the assignment, so nothing carries forward. the shared collector now composes the url in its first capture, so the class no longer needs a per-challenge step.

lessons

solve times

public scoreboard · day 29 finish: below top 10

  • 31:39.4single#90 of 144 solvers
  • 33:52.5time trial#87 of 142 solvers
  • 34:38.6mastery#73 of 126 solvers
  • #61team day finishof 116 teams that cleared it, in 34:38.6
  • #7single 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 31m37s 1 0
time trial about 133s 1 0
mastery about 47s 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

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

{generated by a clanker}