Lab) Network Traffic Analysis Investigations Solution Flashcards
Q1
Question 1 - PCAP 1 - Identify the first evidence of host discovery scanning on the network (prior to TCP). What is the IP address and what is the protocol used?
Opening the first PCAP we can immediately see Address Resolution Protocol (ARP) traffic. Based on the ‘Info’ column we can see that 192.168.56.1 is broadcasting on the network, asking every IP in the subnet (192.168.56.2 to 192.168.56.254) what their associated MAC address is. This is a form of network enumeration that allows an actor to identify online systems within the network when they reply to the ARP request with their MAC address.
Q2
Question 2 - PCAP 1 - What IP address is being port-scanned by the malicious IP?
In the question we’re told that one system is being port-scanned. Based on this information it is highly likely that the attacker’s system is attempting to connect to a target system on a large number of ports. Going to Statistics > Conversations we can see that the source IP 192.168.56.1 (column 1) is connecting to random destination ports (column 4) on destination IP 192.168.56.111 (column 3), where each of these conversations is two packets long (column 5). This is clear evidence of port scanning where the target is 192.168.56.111.
Q3
Question 3 - PCAP 1 - Take a closer look at some of the packets associated with FTP traffic. How many users are allowed to connect to the FTP server at once?
Filtering on FTP traffic only using the filter “FTP” we can see a few response packets that provide informational text to the requesting client. Clicking on one we can see in the bottom pane there is text that mentions how many users can have active sessions at once.
Q4
Question 4 - PCAP 1 - The attacker tries to log into the FTP server using the username “anonymous”. What incorrect password is supplied?
Keeping our filter just looking at FTP traffic we can see a request is made by 192.168.56.1 to the FTP server running on 192.168.56.111 with the username anonymous. It’s important to remember that FTP is an insecure protocol, meaning we can see usernames and passwords in plaintext. We’re asked to find the password supplied during this authentication attempt - we can either keep scrolling down the packet list, or we can right-click the highlighted packet and Follow > TCP Stream.
In the below screenshot we can see that the client provided the server with the user ‘anonymous’ then the password ‘IEUser@’, which resulted in a failed authentication.
Q5
Question 5 - PCAP 1 - Export the robots.txt 404 page from packet 4612 as a HTTP Object and open the text file. What is the version number of Apache running on 192.168.56.111?
We’re provided with the packet number, and based on the question we know it’s HTTP traffic, so we’ll filter using ‘http’ then find packet 4612.
In this packet the system running a web server (192.168.56.111) is sending a 404 page not found response back to the requesting client (192.168.56.1). Using Wireshark we can retrieve the HTML file used to generate the 404 webpage that the client will see. Going to File > Export Objects > HTTP we can see HTML pages captured in the PCAP and export them.
Q5 contd
Looking at the Packet column we can find 4612 and select ‘Save’ then save it our Desktop. Opening the file we can see the web server framework, Apache, and version, 2.4.38.
Q6
Question 6 - PCAP 2 - What IP address downloaded the ZIP file?
Moving to PCAP 2 we know that a ZIP file was downloaded, and the most likely protocol is going to be HTTPso we’ll go to File > Export Objects > HTTP. Looking at the window we can see there is a ZIP file based on the Content Type column showing ‘application/zip’. If the ZIP didn’t show up here, we would go to File > Export Objects, and look at the other options such as SMB, SFTP, etc.
Clicking on the row in the popup will take us to the correct packet within the capture, so we can now close this window and look at the main window. We’re looking at the 200 response from the server (source = 192.168.56.1) back to the client that is requesting to download the file (destination = 192.168.56.111).
Q6 contd
To view the entire conversational better we will right-click the packet and select Follow > TCP Stream. We can now see the red section that shows the GET request from the client at 192.168.56.1, and the blue section that shows the OK 200 response from the server at 192.168.56.111, and then the file contents are transferred to the client.
Q7
Question 7 - PCAP 2 - What is the source port (server) and destination port (client) for the file download?
Continuing on from Q6 we’ll select the packet where the server provides a 200 and sends the content of the ZIP to the client (if you’ve lost the packet go to File > Export > HTTP > click on the ZIP entry to select it, then close the popup window).
In the above screenshot we can see within the TCP layer the source (server) and destination port (client).
Q8
Question 8 - What is the filename of the downloaded zip file?
Based on the analysis we’ve done in the previous 2 questions, we know that filename is cr4ckx0r.zip.
Q9
Question 9 - PCAP 2 - Export the ZIP file and save it to your system. What are the first 5 characters of the MD5 hash value of the ZIP file?
Using File > Export > HTTP, then saving cr4ckx0r.zip to the Desktop we can open a terminal, use bash to get a bash shell, then run md5sum cr4ckx0r.zip to get the hash value.
Q10
Question 10 - PCAP 2 - What is the name of the file inside the ZIP? (without file extension)
We can view the files inside the ZIP by simply double-clicking the ZIP icon which will open it in xarchiver. We can see that the file inside is named ‘hashcat’, a popular offensive/auditing tool used to crack hashes and passwords to reveal the plaintext versions.
Q11
Question 11 - PCAP 2 - What are the first 5 characters of the MD5 hash value of the file inside the ZIP?
We can extract the file by right-clicking the ZIP icon and selecting ‘Extract Here’ to save it to the Desktop. We’ll then open a terminal, type bash, then use md5sum hashcat to get the answer we need.
Q12
Question 12 - PCAP 3 - What IP address is running an FTP server?
Moving to PCAP3, to look only at FTP traffic we’ll use the filter ftp to remove any unrelated noise. We’re looking for the server’s IP address, so we need to pay attention to the Info column to understand what’s happening, and then use the Source and Destination columns to get the server IP.
In the above screenshot we can see a number of FTP packets containing Response: 220. In the screenshot below we can expand the FTP section and get more information about what the 220 response code means.
So know we know that this packet represents the FTP server sending a response message to a client that is attempting to initiate a connection. From this information we know that the source IP must be the server, because it is sending responses to requests. The FTP server IP is 192.168.56.118.
Q13
Question 13 - PCAP 3 - At what time does the attacker send the first password in a dictionary attack against the FTP server?
Scrolling down the packets with our ftp filter still applied, we’ll come across packets that contain ‘PASS’ followed by a value, which represents a password submitted to the server.
But, looking at the Time column, we can see the value is 0.46195… - this value is the time elapsed since the first packet was captured. As the question is asking for the time in the format YYYY-MM-DD HH:MM:SS we need to change how this column is formatted. We’ll do this by going to View > Time Display Format > Date and Time of Day (first option at the top).
Following the requested format, the answer is 2020-05-26 14:51:19.