Just Packets
For this challenge, we are given a traffic.pcap to use with Wireshark!
Opening the file with Wireshark, there is only 20 packets so not a lot to look through.
Looking at the home screen, there are a few packets with clear Base64 content:

Grabbing the content and decoding, itโs a lot ofโฆ nothing interesting. Itโs a story with no flag :<
Arrowing up and down through the packets, I notice that one particular portion is changing every time with readable content, the tcp.urgent_pointer!
In packet 6 it is da, in packet 7 it is wg, in packet 8 it is CTโฆ
Letโs use tshark to automate this:
$ tshark -r traffic.pcap -Y "tcp && frame.number >= 6" -T fields -e tcp.urgent_pointer
25697
30567
17236
18043
30313
27756
24935
25970
29535
25199
28260
29565
10
0
0
This works but we donโt want to manually decode itโฆ Letโs use some bash to do the decoding:
$ tshark -r traffic.pcap -Y "tcp && frame.number >= 6" -T fields -e tcp.urgent_pointer | 130 โต
while read -r val; do
high=$((val >> 8 & 0xFF))
low=$((val & 0xFF))
printf "\\$(printf '%03o' $high)\\$(printf '%03o' $low)"
done
dawgCTF{villagers_bonds}
Flag: dawgCTF{villagers_bonds}
Related Writeups
Chunked Integrity
This is one of my favorite images! Unfortunately something has gone wrong and I cant see the whole thing, can you help f ...
Keeping on Schedule
One of our computers on the company network had some malware on it. We think we cleared of the main payload however it c ...
Stingray Sniper
My Rayhunter has only been in operation for about 3 months, yet it's alerted 4 times! The EFF warns that Rayhunter packe ...