WEBVTT

00:00.740 --> 00:05.140
Hey Guys welcome to capturing network traffic with wireshark.

00:05.150 --> 00:08.090
Previously we introduced network forensics.

00:08.090 --> 00:13.370
Now we're going to introduce Wireshark and show a practical scenario of acquiring or capturing network

00:13.370 --> 00:16.450
packets using this popular and effective tool.

00:16.580 --> 00:22.730
Wireshark is a wide open source tool for capturing filtering and analyzing network traffic and is installed

00:22.730 --> 00:24.570
by default and Kelly Linux.

00:24.620 --> 00:27.160
Wireshark is the successor of death or real.

00:27.320 --> 00:33.770
Originally released in 1998 it allows to capture Packett on any type of network interface provided admin

00:33.770 --> 00:39.230
privileges and the support of the network card for packet sniffing which is also called promiscuous

00:39.230 --> 00:39.870
mode.

00:39.920 --> 00:43.760
Besides capturing wireshark is also a powerful packet analyzer.

00:43.760 --> 00:45.870
It supports several network protocols.

00:46.110 --> 00:51.860
It's based on the lippie kept libraries the same way which also the popular Selye tool TCAP dump is

00:51.860 --> 00:52.870
based.

00:53.060 --> 00:57.950
For more info about wireshark we can refer to the official Web site wireshark dot org.

00:58.160 --> 01:03.740
Let's run Wireshark and explore its interface and main features particularly those relative to the network

01:03.740 --> 01:06.020
traffic capture to run the program.

01:06.050 --> 01:12.230
We click on the Applications menu then on sniffing at spoofing and wireshark the main window shows the

01:12.230 --> 01:17.330
capture mode with a list of network interface is available on the system and the relative graphs on

01:17.330 --> 01:20.000
the right hand showing their activities.

01:20.000 --> 01:24.950
If we move the mouse on the graph or on the name of the interface we see the details such as IP and

01:24.950 --> 01:26.390
MAC addresses.

01:26.720 --> 01:31.500
If we want to start capturing traffic we must select an interface and then click on the relative icon.

01:31.520 --> 01:34.390
Start capturing packets.

01:34.490 --> 01:39.880
We can also set filters on the capture traffic using the preconfigured ones or creating new ones.

01:41.960 --> 01:51.560
To do that we click on capture capture filters that we could select the preconfigured filter or create

01:51.620 --> 01:54.290
a new one by clicking on the plus sign.

01:54.440 --> 02:00.140
The filters can be based on the protocol the IP address and or the port.

02:00.160 --> 02:07.450
Clicking on capture options we can manage the network interface and configure the settings about the

02:07.450 --> 02:11.830
output capture file and the display options and name resolution.

02:11.830 --> 02:16.900
We're going to see a practical scenario of capturing the traffic generated by a simulated exploitation

02:16.960 --> 02:19.560
of a vulnerability and a Unix daemon.

02:19.660 --> 02:26.470
The unreal I.R.S. daemon to do so we use an intentionally vulnerable virtual machine métis point table

02:26.470 --> 02:33.140
2 which also has this vulnerable daemon exposed menace multi-table to can be downloaded from this page.

02:35.570 --> 02:42.080
A tutorial on how to install Mehta's play table 2 on a virtual box host only network VM is available

02:42.080 --> 02:43.560
at this page.

02:43.670 --> 02:46.450
We start the Mehta's ploy table 2 virtual machine.

02:46.700 --> 02:53.330
If we click on the network settings we notice that the network adapter is attached to the host only

02:53.330 --> 02:58.730
network and the associated virtual interface on the host named the box.

02:58.730 --> 03:00.530
Net Zero.

03:00.620 --> 03:09.730
Now we log into the métis point VM with NSF admin username and password.

03:09.850 --> 03:21.470
We execute the config tool to check the IP address associated with the network interface of the VM.

03:21.500 --> 03:28.760
We noticed that the IP address is one eighty two point one sixty eight point fifty six point 101.

03:28.760 --> 03:35.270
We go back to Wireshark and select the host virtual interface V box net zero that has the IP address.

03:35.270 --> 03:44.330
One ninety two point 168 point 5.6 point one to start capturing on this interface we click on the button

03:44.330 --> 03:46.430
with the shark fin.

03:46.640 --> 03:52.790
Now we open the métis poit console in a shell on the Kelly Linux host running the command and have console

04:02.220 --> 04:07.160
running the command MSF Consul a consul with the MSF prompt should appear.

04:07.230 --> 04:15.920
We select the exploit to use with the use command.

04:16.010 --> 04:21.080
When we selected the exploit we can look at the corresponding modules available options with the options

04:21.080 --> 04:26.070
command.

04:26.160 --> 04:32.340
We noticed that the remote port our port is already set to the default I.R.S. port 6 6 6 7 while the

04:32.340 --> 04:35.140
remote host IP is not set.

04:35.340 --> 04:36.900
We set it with the set command

04:40.540 --> 04:45.730
the IP address is the one associated to the network interface of the VM which is one ninety two point

04:45.940 --> 04:51.010
sixty eight point fifty six point one to one.

04:51.030 --> 04:54.190
Now we execute the run command to execute the exploit.

05:04.920 --> 05:08.980
The result is that the exploit response always binds shell with the target.

05:09.030 --> 05:12.540
So we execute command on it with the root privilege.

05:12.540 --> 05:16.640
For example we can do directory listing and display the etc password file

05:20.020 --> 05:22.190
and display the password file.

05:26.380 --> 05:32.890
We go back to Wireshark and stop capturing clicking on the red stop button as you notice.

05:33.010 --> 05:38.750
Wireshark displays the list of capture packets with all the relative info in the upper Panne while the

05:38.750 --> 05:44.670
middle Panchos the packets details and the lower Panchos the hexadecimal view of the packets.

05:44.720 --> 05:50.010
We save the capture traffic to an output file with the opposite button.

05:50.120 --> 05:58.760
We get the file name as attack and save it in the default output format which is picaxe dash MGE.

05:58.800 --> 06:05.130
Great job in this video we introduced Wireshark and showed a practical scenario for capturing network

06:05.130 --> 06:10.420
traffic between two hosts between two hosts on the same network in the next video.

06:10.440 --> 06:13.850
We'll see how to analyze capture network traffic with wireshark.
