WEBVTT

00:00.530 --> 00:06.080
Here everyone welcome to network traffic analysis with wireshark in this video we're going to show how

00:06.080 --> 00:10.670
to use wireshark to analyze the traffic capture from the attack scenario simulated.

00:10.670 --> 00:16.610
In the last video which was capturing network traffic with wireshark that's where we used métis plate

00:16.730 --> 00:23.000
to exploit the vulnerability of an I.R.S. daemon on the display table to V.M. to spawn a root shell

00:23.090 --> 00:24.190
and execute commands.

00:24.190 --> 00:30.200
With root privilege in this video we assumed to know nothing about the attack and we take the role of

00:30.200 --> 00:35.660
a network forensic analyst that must reconstruct the incident examining the traffic captured during

00:35.660 --> 00:42.910
the attack to begin we acquired PCA PMG file in Wireshark.

00:43.020 --> 00:49.540
We should see the made window divided into three pans the top and shows the list of capture packets

00:49.630 --> 00:57.010
and the related info such as the source and destination IP addresses the protocol the length and so

00:57.010 --> 00:57.490
on.

00:58.870 --> 01:03.850
The middle Panchos the details of the packets while the lower pan shows the hexadecimal view of the

01:03.850 --> 01:04.950
data content.

01:05.170 --> 01:11.110
Selecting a packet we could see in the middle Panne the details about the headers or the protocols started

01:11.110 --> 01:17.520
from the lower layer on the top which is data link up to the higher layers network and TradeSports layers.

01:19.230 --> 01:25.740
For example this pacu does the AARP request made by the attackers host to the target machine that has

01:25.740 --> 01:29.900
this target IP address and requesting for the target mac address.

01:31.010 --> 01:32.040
Before in the packet.

01:32.060 --> 01:39.220
Is the reply sent by the target machine from the attackers host with its MAC address.

01:39.400 --> 01:44.170
The next three packets from the three way handshake that initiates the TCAP connection from the attackers

01:44.170 --> 01:49.680
host to the I.R.S. daemon on port 6 6 6 7.

01:50.030 --> 01:55.550
We can observe the typical sin sin ack ack sequence of the three way handshake.

01:55.790 --> 02:02.330
Right clicking on one of these packets and then select bhalo TCAP stream ballista TZP packets are filtered

02:02.330 --> 02:08.020
to display only those belonging to that connection as we could see in the top pan.

02:08.150 --> 02:13.220
This feature gives us a clear view of the data exchange between the attacker and the target.

02:13.220 --> 02:14.970
We also show the data in the window.

02:14.980 --> 02:20.730
In other formats for example in hexadecimal and then save them to an output file.

02:28.670 --> 02:32.180
In particular we can observe the payload highlighted in red.

02:32.600 --> 02:38.660
This payload opens a reverse bind or connect back shell on the target exploiting a backdoor on the I.R.S.

02:38.660 --> 02:39.590
daemon.

02:39.590 --> 02:40.610
Clicking on the payload.

02:40.610 --> 02:44.270
The packet that contains the payload is highlighted in the main window.

02:44.360 --> 02:45.810
We could copy its contents.

02:45.830 --> 02:52.430
Right clicking on it and then selecting for example copy bytes as hex plus A.S.C. I'd dump

02:55.130 --> 02:57.890
then open a text editor and pasting the contents

03:03.270 --> 03:08.280
the following TCAP packets are related to the connection made by the reverse bind shell to the attackers

03:08.280 --> 03:16.670
machine on port 4 4 4 4 if we reichlich on this packet for example and select follow TCAP stream.

03:16.890 --> 03:23.560
We see that the attacker executes some commands with root privileges on the target.

03:23.610 --> 03:28.980
Clicking on file export packets dissection we can export all the packets and their details in various

03:28.980 --> 03:32.640
formats like plaintext CXXVI and so on.

03:34.490 --> 03:35.270
Awesome.

03:35.330 --> 03:40.070
We've just seen a brief example of networked forensic analysis using Wireshark and hope.

03:40.070 --> 03:45.620
This has been enough to show the power and effectiveness of this valuable tool if you like to practice

03:45.620 --> 03:46.540
more with it.

03:46.540 --> 03:47.120
Why are sharks.

03:47.120 --> 03:52.040
Wiki provides several sample packet captures downloadable from this page.

03:52.310 --> 03:58.310
All right in this section we introduce network forensics and the fundamental theory of networking particularly

03:58.310 --> 04:00.500
the TCAP IP protocol suite.

04:00.500 --> 04:05.460
Then we covered the capturing and the following analysis of network traffic with wireshark.

04:05.630 --> 04:09.230
In the next and final section we're going to discuss the reporting phase.
