Challenge: Double Fried · CTF: GPN CTF 2026 · Category: Miscellaneous · Difficulty: Easy
Summary
A .pcap of RFC 5424 syslog messages leaks a flag one character per packet, but
the characters arrive out of order. The packets’ Message ID field holds the
true sequence — sort by it and the flag falls out. The “double-fried” theme
(reverse/transposition cipher) is a red herring.
Solution
Step 1: Identify the per-character syslog stream
kitchen_log.pcap is 115 UDP syslog packets. 96 of them each carry a single
flag character, but in capture order they are scrambled
(GNPTC{FN0tN 1Ec ,Yuo4...). Tempting cipher ideas (pair-swap, reverse,
columnar transposition) all dead-end — pair-swapping even produces the
GPNCTF{ prefix but the phase is inconsistent across the string.
Dumping one packet’s full structure reveals the real ordering key:
| |
Each char packet has a Message ID (R0016, R0017, …). Capture order is
shuffled; the msgid is the intended sequence.
Step 2: Reassemble by Message ID
| |
Output:
| |
A troll line (N0t 4lm0st but n0t qu1t3. H1nt: 1t 15 m3 :)) is interleaved and
sorts ahead due to msgid wraparound — the actual flag is the GPNCTF{...} part.
Flag
| |