Listen

Basic packet sniffing and analysis

Challenge

The quieter you become, the more you are able to listen.

Author: f4lc0n

Solution

Upon connecting to the VPN, I started sniffing for packets using Wireshark (the challenge name kind of gave it away!).

172.30.0.8 is constantly trying to initiate connections to some seemingly random ports on our machine. Obviously, those ports aren't open, so our machine sends an RST, and no connection is established.

Listening on any of these ports gives us a lot of lorem ipsum text.

If we look at the statistics, we can see that while the ports are seemingly randomly chosen, two ports (31336 and 31337) are receiving way more traffic than the rest.

I kept listening on port 31337, and eventually, the flag appeared in one of the messages.

The flag is inctf{s0_y0u_finally_d3cid3d_t0_listen!!}