Tactical LogHuntress CTF 2026 // team archive

Days / Day 29 / Metadata Forensics / Trust Issues

DAY 29//LANE: METADATA FORENSICS//STATUS: CORRECT x3

Trust Issues

SSTTMM Modes reported CORRECT in this write-up

Trust Issues - Day 29 (metadata-forensics) - agent-4

Challenge id: metadata-forensics-day-29-trust-issues Prompt: "Certificates appear in binaries, packages, mail, captures, and disk images. Fingerprint each one, collapse duplicates, and identify the trust claim unsupported by evidence."

Results (from the local runner ledger)

ModeResultTimeFlag
Single SolveCORRECT4.1 sToken84ac96c5f081e2b5e9ce2505ecddcf32
Time TrialCORRECT7.3 sToken4a38b43147f0f46903b520b38f6d960f
MasteryCORRECT7.0 sToken2baf68cb907b0e36b40c87a795499e6c

The runner (not me) made every GM call. I analysed bytes, edited the per-challenge journal and stayed off the GM.

Single Solve method

  • Artifact: single_0.bin (challenge artifact, not published), 672 bytes, a ZIP (metadata-day-29-evidence.zip (challenge artifact, not published)) holding one member, certificate-001.pem.
  • Question: d29-x509-001-x509-sha256-fingerprint - "Determine x509.sha256_fingerprint for certificate-001.pem", exact 64-hex, case-insensitive.
  • Recipe: base64-decode the PEM body to DER, SHA-256 the DER bytes, print lowercase hex. The field key is x509.sha256_fingerprint; the shared adapter did not list it in FIELDS but resolved it through the GM-confirmed alias x509.fingerprint_sha256 (kb/field_recipes). The fingerprint is of the certificate DER, not of the PEM text or the zip member.

How Time Trial and Mastery differed

  • Both are cumulative recaps in an evidence.zip (challenge artifact, not published) (Mastery: 13 sets of ~34 ids, 442 ids in total, bundled in an ~8.7 MB artifact).
  • Time Trial had 34 ids: roster filename, evidence-note size/MD5/SHA-1/SHA-256/magic-16/BOM flag, the Day 4-28 field tokens (jpeg, png, pdf, zip x2, pe x3, dotnet, msi, lnk, ooxml, email, audio, video, elf, macho, apk, jar, sqlite, evtx, registry, prefetch, pcap, disk), the Day 29 x509 fingerprint, and the synthesis question metadata-day-29-synthesis-sha256-order (file names sorted by ascending full-file SHA-256, compact JSON array).
  • Mastery added per-set variants: renamed evidence-note copy filename/size/digests, roster size/digests, and evidence-note filename questions.
  • Recipes per family: digests/size/magic from the member's raw bytes; filenames from the zip listing (roster = the member whose basename starts with roster; renamed copy = the member with identical bytes to the evidence note under another name); format fields via the same autosolve_metadata extractors proven on Day 28 (24/24 offline test); synthesis = sort named files by their SHA-256 hex.
  • Answers were derived from each attempt's own bytes. Single Solve values were never reused.

Timeline / what held the timed modes

  1. Runner first HELD Time Trial: the prediction journal did not exist (my fault: it had to be bound before the first timed attempt). I bound it.
  2. HELD: the assignment snapshot carried no TT/MM answer IDs. Commander refreshed it (TT 34 ids, MM 442).
  3. HELD: journal did not cover every id. I filled covered_answer_ids, transform, item shape and evidence after an offline TT-shaped fixture test of the clone matched independent calculations (x509 fingerprint, note digests/size/magic/BOM, pdf version, roster filename, sha256 order). Gate passed.
  4. HELD: prebrief gate flagged roster-filename as "NO extractor" (97.1% coverage). I did not patch the clone, because the extractor already existed and the stand-in was the problem (see lessons). Commander resolved it; TT then went CORRECT in 7.3 s and Mastery followed at 7.0 s. I do not know which change the Commander made.

Structural vs runtime: the offline fixture test is structural; the CORRECT results come from the GM.

LESSONS / RECOMMENDATIONS

  • Missing piece: roster-filename. The adapter's "exact filename" branch already returns the single member of the zip whose basename starts with roster (Day 20 logic). The prebrief gate runs against the Single Solve zip as stand-in; that zip had only certificate-001.pem, and the roster question's artifact is the bare evidence.zip (challenge artifact, not published) (no -> member). contract_preflight.split_unresolved therefore classed it as "NO extractor" instead of "needs real bytes". It was a gate classification gap, not an extractor gap.
  • Stall: the timed modes were HELD across four rounds (journal missing, contract IDs missing, coverage empty, roster false positive). I cannot give an exact wall-clock figure; the runner log shows the first attempt at 09:00:03 and the pass only after the Commander's fix.
  • What would have been faster:
    1. Bind and fill the prediction journal immediately once Single Solve is CORRECT, instead of waiting for the held message (I only did it after the first HELD).
    2. Have the release assignment carry TT/MM answer ids at stage time; the gate cannot pass without them.
    3. In contract_preflight.split_unresolved, treat role-named members (roster, evidence-note copy, evidence-note) that are absent from the stand-in as needs-real-bytes. This is the shared fix; patching the clone to answer without a roster would fabricate data.
    4. Add x509.sha256_fingerprint to FIELDS directly (it currently resolves through an alias recipe) and a fixture to the lane catalog test.
  • Next-day candidate: the layer sequence suggests the recap bundle keeps growing by one field per day; keep the offline TT-shaped fixture test (certificate + roster + note) as a reusable check.