Challenge
Binary RE (Day 03, lane binary-reverse-engineering). Prompt: "A .NET binary is a database wearing a trench coat. Read the CLI metadata tables - methods, strings, signatures - and find where the configuration is stashed." GM id: binary-reverse-engineering-day-03-managed-configuration (single_solve / time_trial / mastery). 24 answer_ids per delivery (Mastery: 48, set1./set2. prefixed).
Artifacts
Password-protected zip (infected) holding d01--variant-N.elf (challenge artifact, not published) (C), d02--variant-N.elf (challenge artifact, not published) (C++ with .hcfg), d03--variant-N.dll (challenge artifact, not published) (.NET) and its runtimeconfig.json.
Triage
Forensic-inventory questionnaire, same family as Day 01 "ELF Aware" and Day 02 "Mangled"; d01/d02 were the already-known public samples (same sha256 as Mangled), d03 is new.
Investigation
- d01: ELF header + section/symbol tables parsed from bytes;
recover_code=mov eax,0x1fa4; ret(8100). - d02:
.hcfg=HCFG+ ver + XOR key + len + CRC32 LE, payload single-byte XOR JSON (key 0x31, CRC 0x6149aa00). - d03: PE32 i386 .NET assembly, metadata version
v4.0.30319. Config is a 379-byte<PrivateImplementationDetails>static array, XOR 0x41 -> JSON (campaign, domain, mutex, url, ...). Found by scanning for XOR of{"campaign". - Formats: reused Day 01/02 accepted spellings; new fields were found with the GM's partial-submit oracle (one field per submit,
accepted+remainingvsincorrect):d03_analysis_format=pe_cli,machine=i386, section names include the leading empty string, symbols = all non-empty.symtabnames in order, disassembly =["mov eax, 8100","ret"].
Flag Recovery
Each mode returned CORRECT from the GM (tokens in state.json).
Flag
- Single Solve Token202f5e320acf2d7f7d5c0f3516464335
- Time Trial Token26f8f67ea85ea8c76d58798c698afd34
- Mastery Token00e7f7b147dc7747424aa92c7baa9f7c
Minimal Reproduction
scripts/solve_tm.py (compute from the attempt's own bytes) run on the Homebase VM with ctf_gm.py; scripts/solve_tm_m.py batch for Mastery.
Lessons Learned
- Partial single-field submits are a per-field oracle; use them on the untimed Single Solve to lock unknown formats.
- Timed modes: avoid long recon starts (deadline ~6s); GM rate-limits bursts (429) - add retry/sleep.
- Pitfall: a flat full-batch
incorrectin TT right after an expired attempt; per-field submits in a fresh attempt succeeded.