WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.400 --> 00:00:10.300
Hello everyone in this part. We will talk about the

1
00:00:10.300 --> 00:00:13.500
 ARP poison and mitam attacks.

2
00:00:14.900 --> 00:00:17.800
Firstly let's talk about the ARP protocol.

3
00:00:17.800 --> 00:00:21.700
 What is ARP protocol Erp

4
00:00:20.700 --> 00:00:24.200
 stands for address resolution protocol?

5
00:00:23.200 --> 00:00:26.400
 So ARP points the

6
00:00:26.400 --> 00:00:29.600
 hardware address of the machine using that IP address

7
00:00:29.600 --> 00:00:32.800
 from a non IP address when the IP

8
00:00:32.800 --> 00:00:35.900
 which means Internet Protocol has a

9
00:00:35.900 --> 00:00:38.800
 datagram or segment to send it has

10
00:00:38.800 --> 00:00:41.900
 to inform the hardware address or to

11
00:00:41.900 --> 00:00:45.200
 Target in the local network to protocol such

12
00:00:44.200 --> 00:00:47.500
 as ethernet at the network layer.

13
00:00:48.200 --> 00:00:51.700
And if IP Internet Protocol

14
00:00:51.700 --> 00:00:54.400
 cannot find the hardware address of

15
00:00:54.400 --> 00:00:57.500
 the target machine in the cache memory of the

16
00:00:57.500 --> 00:01:00.500
 ARP it will use ARP to

17
00:01:00.500 --> 00:01:01.900
 search for this information.

18
00:01:02.800 --> 00:01:05.500
So with a specific IP address in

19
00:01:05.500 --> 00:01:08.800
 hand ARP queries the local

20
00:01:08.800 --> 00:01:11.400
 network. It queries the lock

21
00:01:11.400 --> 00:01:14.100
 Network to learn who owns this IP address.

22
00:01:14.100 --> 00:01:17.600
 This query is sent to the local network by

23
00:01:17.600 --> 00:01:18.000
 broadcast.

24
00:01:19.300 --> 00:01:22.800
Aims to find the MAC address of the machine to reach

25
00:01:22.800 --> 00:01:25.100
 the IP address belongs by querying.

26
00:01:25.700 --> 00:01:29.000
ARP operates below the network layer

27
00:01:28.300 --> 00:01:31.500
 as a part of the interface between the

28
00:01:31.500 --> 00:01:34.700
 OSI Network layer and OSI data

29
00:01:34.700 --> 00:01:35.200
 link layer.

30
00:01:35.900 --> 00:01:38.500
So in this part, we will investigate the

31
00:01:38.500 --> 00:01:41.400
 network traffic in Wireshark that

32
00:01:41.400 --> 00:01:44.800
 I have obtained by performing a real

33
00:01:44.800 --> 00:01:47.600
 ARP poisoning mitam attack.

34
00:01:48.200 --> 00:01:52.300
But first let's examine our scenario.

35
00:01:51.300 --> 00:01:54.500
 We have two host machines here.

36
00:01:55.400 --> 00:01:59.600
And the first one is running Cali Kali

37
00:01:58.600 --> 00:02:00.300
 operating system.

38
00:02:01.500 --> 00:02:04.200
And this is the machine that will do

39
00:02:04.200 --> 00:02:07.800
 ARP poison or air peace

40
00:02:07.800 --> 00:02:10.500
 proofing attack. The second machine

41
00:02:10.500 --> 00:02:13.400
 is a Windows machine. So, this

42
00:02:13.400 --> 00:02:17.300
 is our Network topology before Erp poisoning

43
00:02:16.300 --> 00:02:19.400
 the IP address of our

44
00:02:19.400 --> 00:02:22.500
 Windows machine and with two dot

45
00:02:22.500 --> 00:02:23.000
 15.

46
00:02:23.900 --> 00:02:27.500
And to make others and Suite 76

47
00:02:26.500 --> 00:02:30.200
 and B6 and there

48
00:02:29.200 --> 00:02:32.400
 is a router the IP address

49
00:02:32.400 --> 00:02:34.700
 and with 2.1.

50
00:02:35.400 --> 00:02:39.400
So they make address and sweet 35 and

51
00:02:38.400 --> 00:02:40.700
 double zero.

52
00:02:41.400 --> 00:02:44.600
As you can see we should focus specifically

53
00:02:44.600 --> 00:02:46.100
 on Mac addresses.

54
00:02:47.300 --> 00:02:48.300
Of each one.

55
00:02:49.700 --> 00:02:52.300
We will focus on the Mac addresses.

56
00:02:53.100 --> 00:02:56.700
And we can consider a sewage between them.

57
00:02:57.300 --> 00:03:00.700
As you can guess here windows and Cali machines

58
00:03:00.700 --> 00:03:03.700
 go to the Internet through this

59
00:03:03.700 --> 00:03:04.200
 router.

60
00:03:04.700 --> 00:03:07.600
So therefore windows and cutting machines

61
00:03:07.600 --> 00:03:09.100
 now this interface.

62
00:03:09.800 --> 00:03:12.800
Of the router which is considered as

63
00:03:12.800 --> 00:03:14.300
 the default gateway.

64
00:03:15.300 --> 00:03:18.900
In other words, they have the IP address and

65
00:03:18.900 --> 00:03:21.800
 Mac address information of this

66
00:03:21.800 --> 00:03:24.100
 interface to see this. Let's look at

67
00:03:24.100 --> 00:03:28.400
 the ARP cache tables of Windows and Cali

68
00:03:27.400 --> 00:03:29.100
 machines in order.

69
00:03:30.500 --> 00:03:33.600
Let's look at the ARP table of Windows first

70
00:03:33.600 --> 00:03:36.400
 here. We see the router with the

71
00:03:36.400 --> 00:03:40.300
 IP address and with 2.1 in

72
00:03:39.300 --> 00:03:42.400
 the first line in here

73
00:03:42.400 --> 00:03:46.000
 this line belongs to the rotor

74
00:03:45.500 --> 00:03:49.100
 information. So and on

75
00:03:48.100 --> 00:03:51.100
 the right side, it is the MAC address.

76
00:03:51.900 --> 00:03:55.300
and sweet 35 and 0

77
00:03:54.300 --> 00:03:55.600
 0

78
00:03:56.300 --> 00:04:00.600
as you have seen before on the topology and it

79
00:03:59.600 --> 00:04:02.500
 ends with 35 and

80
00:04:02.500 --> 00:04:05.300
 0 0 just like we see in the

81
00:04:05.300 --> 00:04:08.900
 topology on the bottom line. We see

82
00:04:08.900 --> 00:04:11.700
 the IP address of the Kali machine

83
00:04:11.700 --> 00:04:14.200
 as you know, and see it

84
00:04:14.200 --> 00:04:17.600
 2.4 and in the

85
00:04:17.600 --> 00:04:20.200
 other column you can

86
00:04:20.200 --> 00:04:24.500
 see it's Mac address and with 64

87
00:04:23.500 --> 00:04:27.900
 and 11 and thus

88
00:04:26.900 --> 00:04:29.900
 we see that Windows has

89
00:04:29.900 --> 00:04:32.400
 information about other machines in our

90
00:04:32.400 --> 00:04:32.800
 Network.

91
00:04:33.700 --> 00:04:34.300
first one

92
00:04:35.200 --> 00:04:36.300
is the rotor.

93
00:04:36.800 --> 00:04:39.700
And the second one is the Cali

94
00:04:39.700 --> 00:04:39.800
 machine.

95
00:04:40.400 --> 00:04:43.400
So Windows knows that the router

96
00:04:43.400 --> 00:04:46.400
 has the IP address ends with

97
00:04:46.400 --> 00:04:49.500
 2.1 and the MAC

98
00:04:49.500 --> 00:04:54.000
 address ends with 35 and 00.

99
00:04:54.900 --> 00:04:57.600
And also knows that the Cali

100
00:04:57.600 --> 00:05:01.400
 machine has the IP address 2.4 and

101
00:05:00.400 --> 00:05:05.400
 the MAC address and sweet 64

102
00:05:03.400 --> 00:05:06.300
 and 11.

103
00:05:07.200 --> 00:05:07.500
so

104
00:05:08.600 --> 00:05:11.500
these informations are so important

105
00:05:11.500 --> 00:05:14.600
 to analyze our network

106
00:05:14.600 --> 00:05:18.400
 and to find the some

107
00:05:17.400 --> 00:05:20.700
 attack a patterns

108
00:05:20.700 --> 00:05:24.300
 on the PK file that we

109
00:05:23.300 --> 00:05:25.700
 will show later.

110
00:05:26.700 --> 00:05:29.700
For example vanity Windows machine wants to

111
00:05:29.700 --> 00:05:32.800
 send a pink packet to Kylie machine.

112
00:05:32.800 --> 00:05:35.500
 The destination IP address of this

113
00:05:35.500 --> 00:05:40.300
 packet will be the others ending with 2.4 while

114
00:05:39.300 --> 00:05:44.600
 the destination Mac address will be 64 and

115
00:05:44.600 --> 00:05:47.400
 11. And now let's look

116
00:05:47.400 --> 00:05:50.600
 at the ARP table of the Cali machine.

117
00:05:52.300 --> 00:05:55.400
Here in the first line. We see the record of

118
00:05:55.400 --> 00:05:59.200
 the Windows machine the first line belongs

119
00:05:58.200 --> 00:06:00.700
 to the Windows machine.

120
00:06:01.500 --> 00:06:05.300
And as the IP address and Suite 2

121
00:06:04.300 --> 00:06:07.700
 dot 15 as you

122
00:06:07.700 --> 00:06:11.700
 saw in the network topology, the Windows

123
00:06:11.700 --> 00:06:14.500
 machine has the IP address and with the

124
00:06:14.500 --> 00:06:17.700
 ends with 2.15 and

125
00:06:17.700 --> 00:06:21.700
 Kali machine knows that

126
00:06:20.700 --> 00:06:23.700
 Windows has this

127
00:06:23.700 --> 00:06:26.400
 IP address and also knows that

128
00:06:26.400 --> 00:06:29.800
 in its Erp cache

129
00:06:29.800 --> 00:06:32.700
 table Windows the MAC

130
00:06:32.700 --> 00:06:35.700
 address of the windows. So Windows has the

131
00:06:35.700 --> 00:06:39.400
 MAC address and with 76

132
00:06:38.400 --> 00:06:41.700
 and B6.

133
00:06:42.600 --> 00:06:46.200
So this is the important point for

134
00:06:45.200 --> 00:06:47.400
 us and

135
00:06:49.400 --> 00:06:53.000
And at the bottom line, the routers information

136
00:06:52.600 --> 00:06:55.300
 is kept you can see

137
00:06:55.300 --> 00:06:55.800
 in here.

138
00:06:57.400 --> 00:06:59.100
and with the IP address

139
00:07:01.400 --> 00:07:04.600
and speed 2.1 this IP

140
00:07:04.600 --> 00:07:06.800
 address belongs to the rotor.

141
00:07:07.400 --> 00:07:10.300
So and the MAC address of the

142
00:07:10.300 --> 00:07:13.500
 router is this Mac address

143
00:07:13.500 --> 00:07:14.300
 and

144
00:07:15.400 --> 00:07:19.200
It ends with 35 and 0

145
00:07:18.200 --> 00:07:19.400
 0.

146
00:07:20.400 --> 00:07:21.300
You can see here.

147
00:07:22.200 --> 00:07:25.500
So the Cali machine has the information

148
00:07:25.500 --> 00:07:29.000
 about the windows and the

149
00:07:28.000 --> 00:07:29.400
 router.

150
00:07:29.900 --> 00:07:32.600
And Kylie knows that win

151
00:07:32.600 --> 00:07:35.900
 colonos the windows

152
00:07:35.900 --> 00:07:38.900
 IP and making formations

153
00:07:38.900 --> 00:07:41.600
 and also it knows

154
00:07:41.600 --> 00:07:44.900
 the rotors information about

155
00:07:44.900 --> 00:07:47.900
 its IP address and Mac

156
00:07:47.900 --> 00:07:51.100
 address. So these were

157
00:07:50.100 --> 00:07:53.400
 the ARP cache tables

158
00:07:53.400 --> 00:07:56.300
 of the Cali machine and the Windows

159
00:07:56.300 --> 00:07:59.600
 machine and now let's go back to topology.

160
00:08:01.600 --> 00:08:04.600
When a message or a network packet is sent

161
00:08:04.600 --> 00:08:07.700
 from the Windows machine to the

162
00:08:07.700 --> 00:08:11.000
 internet. Let's say this packet

163
00:08:10.200 --> 00:08:13.900
 or when there is a network packet

164
00:08:13.900 --> 00:08:16.600
 coming from the internet to the

165
00:08:16.600 --> 00:08:17.600
 Windows machine.

166
00:08:18.500 --> 00:08:21.500
As you know, the router must know the MAC address

167
00:08:21.500 --> 00:08:24.700
 of this Windows machine in order to provide or

168
00:08:24.700 --> 00:08:27.500
 in order to provide this traffic or

169
00:08:27.500 --> 00:08:32.100
 to forward this packets and

170
00:08:30.100 --> 00:08:33.500
 just like the

171
00:08:33.500 --> 00:08:36.700
 information of the router in the windows ARP table.

172
00:08:37.800 --> 00:08:40.500
And after the network, the connection

173
00:08:40.500 --> 00:08:43.700
 between Windows and routers is

174
00:08:43.700 --> 00:08:46.500
 established ARP communication is

175
00:08:46.500 --> 00:08:48.300
 already made between them.

176
00:08:49.200 --> 00:08:52.400
So as a result, they have each other's

177
00:08:52.400 --> 00:08:55.300
 IP and make mapping or

178
00:08:55.300 --> 00:08:59.500
 matching information. So Windows

179
00:08:58.500 --> 00:09:02.300
 knows that the IP

180
00:09:01.300 --> 00:09:06.400
 and sweet 2.1 belongs

181
00:09:04.400 --> 00:09:08.200
 to the neck address

182
00:09:07.200 --> 00:09:11.600
 and sweet 35 and

183
00:09:11.600 --> 00:09:13.000
 0 0

184
00:09:13.600 --> 00:09:18.100
Windows has this information and fact

185
00:09:16.100 --> 00:09:19.800
 like this on the

186
00:09:19.800 --> 00:09:22.700
 other hand. The router also knows that

187
00:09:22.700 --> 00:09:25.200
 the IP address ends with

188
00:09:25.200 --> 00:09:29.000
 2.15 matches with

189
00:09:28.200 --> 00:09:32.800
 the 76 matches with

190
00:09:32.800 --> 00:09:36.700
 the MAC address and switch 76 and

191
00:09:36.700 --> 00:09:40.100
 P6. In other words Erp communication

192
00:09:39.100 --> 00:09:42.800
 takes place as like this

193
00:09:42.800 --> 00:09:46.400
 Windows machines and ARP broadcast

194
00:09:46.400 --> 00:09:50.200
 squaring a who has and Dot

195
00:09:49.200 --> 00:09:52.400
 10 Dot

196
00:09:52.400 --> 00:09:54.500
 0.2.1.

197
00:09:55.100 --> 00:09:59.100
Tell the IP address of 10

198
00:09:58.100 --> 00:10:03.100
 dots 0.2.15.

199
00:10:03.900 --> 00:10:06.600
So since the machine with an

200
00:10:06.600 --> 00:10:10.300
 IP address and link with 2.1 in

201
00:10:09.300 --> 00:10:13.200
 the network is a router the router

202
00:10:12.200 --> 00:10:16.000
 sends an ARP response and

203
00:10:15.600 --> 00:10:18.100
 the response packet packet is

204
00:10:18.100 --> 00:10:22.300
 like this 10.0 dot

205
00:10:21.300 --> 00:10:24.600
 2.1 is at

206
00:10:24.600 --> 00:10:27.700
 in the in this Mac

207
00:10:27.700 --> 00:10:31.000
 address in this machine and sweet

208
00:10:30.800 --> 00:10:34.100
 35 and 0

209
00:10:33.100 --> 00:10:36.300
 0 does the IP

210
00:10:36.300 --> 00:10:39.800
 address ending with two dot one on

211
00:10:39.800 --> 00:10:42.300
 the Windows machine. That is

212
00:10:42.300 --> 00:10:45.100
 the gateway address is match fit this

213
00:10:45.100 --> 00:10:45.600
 Mac address.

214
00:10:46.600 --> 00:10:48.800
match with this Mac address

215
00:10:50.100 --> 00:10:54.300
and written to the windows Erp

216
00:10:53.300 --> 00:10:56.900
 table this information. So

217
00:10:56.900 --> 00:11:00.300
 likewise the router creates such

218
00:10:59.300 --> 00:11:03.000
 a broadcast to match the IP address

219
00:11:02.400 --> 00:11:06.900
 of the Windows machine and

220
00:11:05.900 --> 00:11:08.800
 with Mac

221
00:11:08.800 --> 00:11:11.500
 address and writes the response to

222
00:11:11.500 --> 00:11:13.700
 its own Erp table.

223
00:11:14.400 --> 00:11:17.500
It does IP address and Mac address

224
00:11:17.500 --> 00:11:21.200
 matching is made on both sides and the

225
00:11:20.200 --> 00:11:23.900
 same communication is done between Cali and

226
00:11:23.900 --> 00:11:24.800
 windows as well.

227
00:11:25.800 --> 00:11:29.400
You know that maybe about the

228
00:11:29.400 --> 00:11:33.400
 Erp protocol. So

229
00:11:32.400 --> 00:11:35.600
 now let's see a similar communication

230
00:11:35.600 --> 00:11:37.900
 example in Wireshark.

231
00:11:39.900 --> 00:11:43.100
And in this pickup file, let's type

232
00:11:42.100 --> 00:11:45.900
 ARP in display

233
00:11:45.900 --> 00:11:48.500
 filter field and filter it

234
00:11:48.500 --> 00:11:50.000
 to see the ARP traffic.

235
00:11:56.300 --> 00:11:58.000
So let's look at this packet.

236
00:11:59.600 --> 00:12:02.400
the machine with the MAC address ending in

237
00:12:04.300 --> 00:12:08.300
six e and BD is

238
00:12:07.300 --> 00:12:10.900
 sending a broadcast you can

239
00:12:10.900 --> 00:12:13.700
 see that we can understand that is broadcasting because

240
00:12:13.700 --> 00:12:16.400
 the destination Mac address consists of

241
00:12:16.400 --> 00:12:19.700
 FF characters. So

242
00:12:19.700 --> 00:12:23.000
 in this broadcast it asks,

243
00:12:22.400 --> 00:12:26.500
 who is the machine whose

244
00:12:25.500 --> 00:12:30.700
 IP address and sweet 1.1?

245
00:12:31.400 --> 00:12:34.900
and asks it to report it to

246
00:12:34.900 --> 00:12:34.900
 the

247
00:12:36.800 --> 00:12:40.700
IP address and link with the one thought

248
00:12:40.700 --> 00:12:41.500
 two

249
00:12:42.200 --> 00:12:45.700
It asks it to report to the

250
00:12:45.700 --> 00:12:49.500
 IP address ending with 1.2 the

251
00:12:48.500 --> 00:12:51.700
 machine whose Mac address and

252
00:12:51.700 --> 00:12:52.500
 Suite.

253
00:12:54.800 --> 00:12:57.600
In the next packet the machine

254
00:12:57.600 --> 00:13:02.100
 whose Mac address ends with 30 for

255
00:13:01.100 --> 00:13:05.400
 and 56. So

256
00:13:04.400 --> 00:13:07.400
 response to this

257
00:13:07.400 --> 00:13:11.100
 query the previous query

258
00:13:10.100 --> 00:13:14.500
 to the previous query with the

259
00:13:13.500 --> 00:13:16.900
 RP reply message you can

260
00:13:16.900 --> 00:13:19.800
 see it is a reply message and

261
00:13:19.800 --> 00:13:22.200
 it replies to the

262
00:13:22.200 --> 00:13:24.200
 to the previous query.

263
00:13:24.900 --> 00:13:27.600
About the IP address and

264
00:13:27.600 --> 00:13:30.300
 with 1.1.

265
00:13:31.400 --> 00:13:35.500
And in the reply of 34 56,

266
00:13:34.500 --> 00:13:37.800
 it says that the

267
00:13:37.800 --> 00:13:41.700
 IP address ends with 1.1 belongs

268
00:13:40.700 --> 00:13:42.100
 to me.

269
00:13:42.900 --> 00:13:45.700
So it knows now that

270
00:13:45.700 --> 00:13:48.200
 this IP address belongs to

271
00:13:48.200 --> 00:13:50.300
 this machine.

272
00:13:51.400 --> 00:13:54.500
That has the MAC address and

273
00:13:54.500 --> 00:13:59.100
 with 34 and 56 and

274
00:13:57.100 --> 00:14:00.500
 it was a simple

275
00:14:00.500 --> 00:14:04.000
 and usual example of Erp communication.

276
00:14:03.700 --> 00:14:06.800
 Now we can close this pickup

277
00:14:06.800 --> 00:14:09.500
 file. Now. Let's see a huge internet

278
00:14:09.500 --> 00:14:13.400
 traffic on our topology and

279
00:14:12.400 --> 00:14:15.600
 I have captured before

280
00:14:15.600 --> 00:14:19.100
 in Wireshark and normal a

281
00:14:18.100 --> 00:14:22.700
 usual internet traffic and we

282
00:14:22.700 --> 00:14:25.600
 will look at our machines internet traffic

283
00:14:25.600 --> 00:14:28.900
 in Wireshark. So let's open the peak

284
00:14:28.900 --> 00:14:31.100
 file that I have captured before.

285
00:14:32.100 --> 00:14:34.500
and in this pickup file

286
00:14:35.100 --> 00:14:39.200
Let's look at a normal usual internet

287
00:14:38.200 --> 00:14:40.300
 traffic example.

288
00:14:42.700 --> 00:14:45.300
So for example, let's look at this packet.

289
00:14:46.600 --> 00:14:50.000
The IP address ending with

290
00:14:49.700 --> 00:14:53.700
 two Dot 4 belong

291
00:14:52.700 --> 00:14:55.300
 to the Cali machine, you know,

292
00:14:55.300 --> 00:14:58.800
 the calcium sense a

293
00:14:58.800 --> 00:15:01.500
 TCP packet to the

294
00:15:01.500 --> 00:15:07.200
 IP address and Suite 237

295
00:15:04.200 --> 00:15:08.100
 and

296
00:15:07.100 --> 00:15:10.700
 2309.

297
00:15:11.400 --> 00:15:14.600
That is to an address outside

298
00:15:14.600 --> 00:15:18.400
 the network on the internet. However, when

299
00:15:17.400 --> 00:15:20.000
 we look at the destination Mac address

300
00:15:20.900 --> 00:15:22.200
in this packet

301
00:15:23.300 --> 00:15:26.400
Let's look at the packet details.

302
00:15:28.100 --> 00:15:28.900
in this packet

303
00:15:29.500 --> 00:15:32.500
when we look at the destination Mac address

304
00:15:33.400 --> 00:15:34.000
we can see.

305
00:15:37.200 --> 00:15:41.100
the destination Mac address and with

306
00:15:40.100 --> 00:15:44.100
 35 and 0

307
00:15:43.100 --> 00:15:44.600
 0

308
00:15:45.600 --> 00:15:48.300
so this address is the MAC address

309
00:15:48.300 --> 00:15:49.000
 of the router.

310
00:15:50.500 --> 00:15:53.500
And therefore it sends

311
00:15:53.500 --> 00:15:56.600
 this packet to the router to send the

312
00:15:56.600 --> 00:16:01.000
 packet to the address to 37

313
00:15:59.800 --> 00:16:03.500
 to 39. The

314
00:16:02.500 --> 00:16:05.800
 router will receive this packet

315
00:16:05.800 --> 00:16:08.900
 and forward it to the destination IP

316
00:16:08.900 --> 00:16:09.200
 address.

317
00:16:12.300 --> 00:16:15.600
And if we hadn't look

318
00:16:15.600 --> 00:16:18.800
 at the destination Mac address, we wouldn't

319
00:16:18.800 --> 00:16:21.500
 have noticed this detail. We will

320
00:16:21.500 --> 00:16:24.300
 understand better. How important this detail

321
00:16:24.300 --> 00:16:27.900
 is when we look again after ARP poisoning.

322
00:16:27.900 --> 00:16:30.500
 Okay, and this is

323
00:16:30.500 --> 00:16:33.900
 how to dot for

324
00:16:33.900 --> 00:16:36.400
 the color machine send the

325
00:16:36.400 --> 00:16:39.800
 packet to the destination over the

326
00:16:39.800 --> 00:16:40.200
 rotor.

327
00:16:41.500 --> 00:16:45.000
Now, let's look at the next packet when we

328
00:16:44.100 --> 00:16:47.600
 look at the next packet. This packet

329
00:16:47.600 --> 00:16:52.200
 comes from the IP address and

330
00:16:50.200 --> 00:16:54.600
 with 237 and

331
00:16:54.600 --> 00:16:57.600
 239 and this IP

332
00:16:57.600 --> 00:17:00.700
 address belongs to the previous Target

333
00:17:00.700 --> 00:17:04.200
 others on the internet. Now the

334
00:17:03.200 --> 00:17:06.600
 packet comes from this IP

335
00:17:06.600 --> 00:17:09.300
 address and an application data packet

336
00:17:09.300 --> 00:17:12.600
 is coming to two dot

337
00:17:12.600 --> 00:17:16.300
 four from two thirty

338
00:17:15.300 --> 00:17:18.300
 seven, two thirty nine

339
00:17:18.300 --> 00:17:21.300
 Source IP address, but if you look

340
00:17:21.300 --> 00:17:22.500
 at the mechanics,

341
00:17:23.400 --> 00:17:26.900
Of the source IP address we see

342
00:17:26.900 --> 00:17:29.700
 that it ends with a 35

343
00:17:29.700 --> 00:17:31.300
 and 0 0.

344
00:17:31.900 --> 00:17:34.300
But this address is the MAC address

345
00:17:34.300 --> 00:17:37.400
 of the router. Yes, because the packet from

346
00:17:37.400 --> 00:17:41.500
 the coming incoming

347
00:17:40.500 --> 00:17:44.200
 packet from this IP address Arise at

348
00:17:43.200 --> 00:17:48.100
 the router first and router

349
00:17:46.100 --> 00:17:50.300
 forwards this pack

350
00:17:49.300 --> 00:17:53.000
 to the IP address with

351
00:17:52.300 --> 00:17:56.200
 two dot for which

352
00:17:55.200 --> 00:17:59.400
 is which belongs to the Kylie machine

353
00:17:59.400 --> 00:18:02.800
 and the destination machine is Kelly

354
00:18:02.800 --> 00:18:06.700
 with ip2.4. You

355
00:18:05.700 --> 00:18:08.200
 can see that the MAC address

356
00:18:08.200 --> 00:18:09.100
 and sweet.

357
00:18:10.800 --> 00:18:13.600
64 and 11. So the

358
00:18:13.600 --> 00:18:17.100
 destination is really Cali machine and this

359
00:18:16.100 --> 00:18:20.000
 is the expected and normal internet traffic.

360
00:18:20.700 --> 00:18:24.200
And now let's talk about how an Erp

361
00:18:23.200 --> 00:18:27.100
 poisoning or mitm attack

362
00:18:26.100 --> 00:18:29.300
 happens Carly is

363
00:18:29.300 --> 00:18:32.100
 our attacker machine will be

364
00:18:32.100 --> 00:18:33.800
 our attacker machine.

365
00:18:34.500 --> 00:18:37.700
Let's look at the on our topology and

366
00:18:37.700 --> 00:18:41.400
 Kali machine will be our middleman and

367
00:18:40.400 --> 00:18:43.800
 Kelly will stand between

368
00:18:43.800 --> 00:18:46.400
 the Windows machine and

369
00:18:46.400 --> 00:18:47.200
 the router.

370
00:18:47.900 --> 00:18:50.500
In the Erp poisoning attack or

371
00:18:50.500 --> 00:18:55.200
 mitmen in the middle attack. Kali

372
00:18:53.200 --> 00:18:56.500
 will turn

373
00:18:56.500 --> 00:18:59.900
 to the rotor and say hey, I

374
00:18:59.900 --> 00:19:03.900
 am the mission with the IP 2.15.

375
00:19:05.100 --> 00:19:09.100
So it will send an ARP reply message like

376
00:19:08.100 --> 00:19:11.500
 this 2.15 is

377
00:19:11.500 --> 00:19:15.000
 at the MAC address 64 and

378
00:19:14.300 --> 00:19:17.800
 11 to the rotor. So which

379
00:19:17.800 --> 00:19:21.700
 64 11 is

380
00:19:21.700 --> 00:19:22.700
 its neck address?

381
00:19:23.300 --> 00:19:26.200
With this message, the router will match the

382
00:19:26.200 --> 00:19:30.500
 IP address ending with two dot

383
00:19:29.500 --> 00:19:34.400
 15 vitically Mac

384
00:19:33.400 --> 00:19:34.600
 address.

385
00:19:35.200 --> 00:19:39.000
In its ARP table the IP

386
00:19:38.200 --> 00:19:41.600
 address 2.15 will

387
00:19:41.600 --> 00:19:44.400
 match with the MAC address of Kali.

388
00:19:44.700 --> 00:19:47.700
The second target of the Kali

389
00:19:47.700 --> 00:19:51.300
 is the Windows machine in The Next Step. Kali

390
00:19:50.300 --> 00:19:53.500
 will turn to the Windows machine.

391
00:19:54.200 --> 00:19:58.600
And it will send an Erp

392
00:19:57.600 --> 00:20:01.100
 reply message directly and

393
00:20:00.100 --> 00:20:03.800
 it will say this. Hey, I

394
00:20:03.800 --> 00:20:06.800
 am the mission with the IP address

395
00:20:06.800 --> 00:20:08.700
 2.1.

396
00:20:09.600 --> 00:20:13.200
So it will send an air purify

397
00:20:12.200 --> 00:20:15.700
 message to dot one

398
00:20:15.700 --> 00:20:19.400
 IP address is at the

399
00:20:18.400 --> 00:20:20.100
 MAC address.

400
00:20:22.100 --> 00:20:24.600
64 and 11

401
00:20:25.600 --> 00:20:29.200
so windows will think Cali is

402
00:20:28.200 --> 00:20:29.800
 a router.

403
00:20:31.800 --> 00:20:34.500
And it will send packets to the Kali.

404
00:20:35.600 --> 00:20:37.900
That it should send to the rotor.

405
00:20:39.600 --> 00:20:42.600
You can imagine this situation like this Windows once

406
00:20:42.600 --> 00:20:45.700
 to send a packet a

407
00:20:45.700 --> 00:20:46.000
 message.

408
00:20:47.400 --> 00:20:50.300
or packet to the internet for example,

409
00:20:50.300 --> 00:20:53.700
 and firstly it will

410
00:20:53.700 --> 00:20:56.700
 send the packet to the router in a

411
00:20:56.700 --> 00:20:58.100
 normal traffic, but now

412
00:21:00.700 --> 00:21:04.700
As a result as a

413
00:21:04.700 --> 00:21:09.000
 result of the Erp poisoning Windows things

414
00:21:08.700 --> 00:21:11.700
 the Cali machine as rooted. So

415
00:21:11.700 --> 00:21:15.100
 when the when when

416
00:21:14.100 --> 00:21:17.700
 it wants to send the

417
00:21:17.700 --> 00:21:18.600
 packet to the rotor.

418
00:21:19.500 --> 00:21:22.700
It will send to the Cali because in the

419
00:21:22.700 --> 00:21:27.100
 ARP table of Windows the

420
00:21:25.100 --> 00:21:28.800
 Mac the IP

421
00:21:28.800 --> 00:21:33.700
 address to ends with 2.1 matches

422
00:21:31.700 --> 00:21:35.000
 with the MAC

423
00:21:34.000 --> 00:21:35.200
 address.

424
00:21:37.900 --> 00:21:39.200
64 and 11

425
00:21:40.200 --> 00:21:43.500
So when it wants to send a packet to the router,

426
00:21:43.500 --> 00:21:46.700
 it will send the packet

427
00:21:46.700 --> 00:21:48.500
 to this Mac address.

428
00:21:50.700 --> 00:21:53.800
Because it believes that the IP

429
00:21:53.800 --> 00:21:56.600
 address matches with this Mac

430
00:21:56.600 --> 00:21:59.800
 address, but this Mac address belongs to

431
00:21:59.800 --> 00:22:01.000
 Cali machine.

432
00:22:01.500 --> 00:22:04.700
So when it sends a packet to this

433
00:22:04.700 --> 00:22:05.100
 IP address.

434
00:22:06.600 --> 00:22:09.300
To send the packet to this Mac

435
00:22:09.300 --> 00:22:09.500
 address.

436
00:22:11.100 --> 00:22:14.400
So to the Kali machine, so as a

437
00:22:14.400 --> 00:22:17.300
 result packets going to

438
00:22:17.300 --> 00:22:19.700
 router from the windows.

439
00:22:20.500 --> 00:22:23.600
And coming from the

440
00:22:23.600 --> 00:22:25.800
 router to Windows machine.

441
00:22:26.800 --> 00:22:28.700
We'll go to the Cali.

442
00:22:30.300 --> 00:22:33.800
Let's say this packet going from the

443
00:22:33.800 --> 00:22:35.400
 windows to the router.

444
00:22:36.300 --> 00:22:40.300
This packet will go to the Cali.

445
00:22:41.300 --> 00:22:44.900
As to result of the ARP poison and the

446
00:22:44.900 --> 00:22:47.500
 packets coming from the router to

447
00:22:47.500 --> 00:22:48.400
 the Windows machine.

448
00:22:49.400 --> 00:22:52.600
Let's say this these packets

449
00:22:52.600 --> 00:22:54.900
 will go to the Kali.

450
00:22:56.200 --> 00:23:00.700
Because the router thinks that the IP

451
00:22:59.700 --> 00:23:05.400
 address 2.15 matches

452
00:23:03.400 --> 00:23:06.900
 with the MAC address

453
00:23:06.900 --> 00:23:09.900
 64 and 11.

454
00:23:10.700 --> 00:23:13.600
So in the ARP table of root

455
00:23:13.600 --> 00:23:17.500
 for the MAC address, sorry the

456
00:23:17.500 --> 00:23:22.000
 IP address 2.15 matches

457
00:23:20.100 --> 00:23:23.900
 with the MAC address.

458
00:23:25.400 --> 00:23:27.200
64 and 11

459
00:23:28.200 --> 00:23:30.200
and when a packet

460
00:23:31.200 --> 00:23:35.100
comes from the internet to the windows the

461
00:23:34.100 --> 00:23:37.600
 router will forward the packet.

462
00:23:39.500 --> 00:23:43.700
To this IP address and in its

463
00:23:43.700 --> 00:23:46.700
 RP table this IP

464
00:23:46.700 --> 00:23:50.100
 address matches with the Cali's Mac

465
00:23:49.100 --> 00:23:54.000
 address. It will send packet to

466
00:23:52.700 --> 00:23:55.500
 this method so

467
00:23:55.500 --> 00:23:57.700
 to the Cali machine.

468
00:23:58.300 --> 00:24:02.100
On the other hand Kali will forward traffic as

469
00:24:01.100 --> 00:24:02.500
 it should.

470
00:24:03.200 --> 00:24:06.100
Because Kelly receives packets from the

471
00:24:06.100 --> 00:24:10.000
 router and forwards them to Windows.

472
00:24:10.800 --> 00:24:15.100
And when the Cali receives when

473
00:24:13.100 --> 00:24:16.500
 the color receives the packets

474
00:24:16.500 --> 00:24:17.800
 from the windows.

475
00:24:20.600 --> 00:24:22.800
It will forward the packets to the rotor.

476
00:24:24.200 --> 00:24:27.900
And in this situation there is no problem or interruption in

477
00:24:27.900 --> 00:24:31.200
 network traffic. So this

478
00:24:30.200 --> 00:24:34.100
 will become nearly impossible

479
00:24:33.100 --> 00:24:37.400
 to monetize that unusual

480
00:24:36.400 --> 00:24:40.700
 situation that the Erp

481
00:24:39.700 --> 00:24:43.000
 poisoning attack and let's

482
00:24:42.300 --> 00:24:45.900
 take a look at what happens during

483
00:24:45.900 --> 00:24:48.600
 Erp poisoning and how

484
00:24:48.600 --> 00:24:52.700
 traffic is manipulated afterwards in Wireshark.

485
00:24:51.700 --> 00:24:54.100
 So let's open the

486
00:24:54.100 --> 00:24:56.900
 pickup file associated with Erp poisoning.

487
00:24:57.600 --> 00:24:59.600
And men in the middle attack.

488
00:25:01.600 --> 00:25:04.800
so we have opened the pickup

489
00:25:04.800 --> 00:25:07.600
 file associated with the RP poisoning and

490
00:25:07.600 --> 00:25:10.600
 in this traffic includes all

491
00:25:10.600 --> 00:25:14.200
 packets from the moment ARP poisoning

492
00:25:13.200 --> 00:25:15.900
 started and

493
00:25:16.900 --> 00:25:19.600
here the first thing

494
00:25:19.600 --> 00:25:22.100
 that takes our attention is there.

495
00:25:23.700 --> 00:25:27.800
Firstly let's remember our machines with their

496
00:25:26.800 --> 00:25:29.900
 Mac address in here.

497
00:25:29.900 --> 00:25:34.200
 You can see the machine as

498
00:25:32.200 --> 00:25:35.100
 the MAC address

499
00:25:35.100 --> 00:25:38.900
 and Suite 76 and P6.

500
00:25:38.900 --> 00:25:41.700
 And this is our Windows machine.

501
00:25:41.700 --> 00:25:44.400
 Maybe you can remember from the

502
00:25:44.400 --> 00:25:48.000
 topology the MAC address 76 and

503
00:25:47.600 --> 00:25:51.000
 P6 belongs to Windows machine.

504
00:25:50.300 --> 00:25:53.400
 So when we see this Mac address,

505
00:25:53.400 --> 00:25:56.200
 they will know that this is the windows.

506
00:25:56.700 --> 00:26:00.800
and when we see the MAC address 35

507
00:25:59.800 --> 00:26:02.500
 and 0 0

508
00:26:04.100 --> 00:26:07.700
we will know that this is the router and when

509
00:26:07.700 --> 00:26:10.600
 we see the MAC address 64 and

510
00:26:10.600 --> 00:26:14.100
 11, we will know that this machine

511
00:26:13.100 --> 00:26:17.200
 is currently so let's

512
00:26:16.200 --> 00:26:19.300
 turn back to the pickup file.

513
00:26:22.200 --> 00:26:25.800
And now you can see that in here

514
00:26:25.800 --> 00:26:30.000
 the first packet associated

515
00:26:28.200 --> 00:26:33.100
 with ARP in

516
00:26:31.100 --> 00:26:35.100
 this packet. The

517
00:26:34.100 --> 00:26:37.500
 source Mac address is the

518
00:26:39.300 --> 00:26:43.400
At the source Mac address is kali's Mac

519
00:26:42.400 --> 00:26:46.000
 address 64 and

520
00:26:45.600 --> 00:26:48.600
 11 and the other Mac address

521
00:26:48.600 --> 00:26:52.000
 belongs to Windows. So Source

522
00:26:51.800 --> 00:26:54.700
 machine is the Kali and

523
00:26:54.700 --> 00:26:58.000
 destination machine is Windows. Let's

524
00:26:57.700 --> 00:27:00.300
 focused in that situation.

525
00:27:00.300 --> 00:27:04.300
 The first packet is a ARP

526
00:27:03.300 --> 00:27:06.600
 reply message ARP reply

527
00:27:06.600 --> 00:27:10.100
 packet, although there is no ARP request

528
00:27:09.100 --> 00:27:12.900
 from Windows machine

529
00:27:12.900 --> 00:27:18.100
 76 and ps6 Cali

530
00:27:15.100 --> 00:27:18.400
 Sands

531
00:27:18.400 --> 00:27:21.900
 reply ARP reply

532
00:27:21.900 --> 00:27:25.000
 message directly and

533
00:27:24.700 --> 00:27:28.500
 moreover. He says that the

534
00:27:27.500 --> 00:27:30.600
 IP ending with

535
00:27:30.600 --> 00:27:32.600
 two dot one.

536
00:27:34.100 --> 00:27:37.000
belongs to it belongs to

537
00:27:39.500 --> 00:27:41.500
its own others

538
00:27:41.900 --> 00:27:44.900
or it says that the IP

539
00:27:44.900 --> 00:27:48.700
 address 2.1 is

540
00:27:47.700 --> 00:27:50.600
 mine mine and

541
00:27:50.600 --> 00:27:51.400
 my IP address.

542
00:27:52.300 --> 00:27:53.600
So it says to Windows.

543
00:27:54.400 --> 00:27:58.100
It says Kelly says to Windows. I am

544
00:27:57.100 --> 00:28:00.800
 the router it is reply message.

545
00:28:01.600 --> 00:28:04.600
And then even if

546
00:28:04.600 --> 00:28:07.500
 we don't know which machine

547
00:28:07.500 --> 00:28:11.300
 the MAC address and link with 64 and

548
00:28:10.300 --> 00:28:14.400
 11 belong belongs

549
00:28:13.400 --> 00:28:16.500
 to it is not normal for

550
00:28:16.500 --> 00:28:19.500
 machine to send an ARP reply message

551
00:28:19.500 --> 00:28:22.900
 directly in this way. Since there is no mechanist

552
00:28:22.900 --> 00:28:25.500
 change on the router if we compare

553
00:28:25.500 --> 00:28:29.700
 this Mac address with the routers Mac

554
00:28:28.700 --> 00:28:29.800
 address.

555
00:28:31.200 --> 00:28:34.300
We can be sure that it is a different machine.

556
00:28:35.600 --> 00:28:38.300
So right after the machine with

557
00:28:38.300 --> 00:28:42.300
 the 64 and 11 cents a

558
00:28:42.300 --> 00:28:46.100
 message another another reply Erp

559
00:28:45.100 --> 00:28:50.600
 reply message to 35

560
00:28:48.600 --> 00:28:51.700
 and 0

561
00:28:51.700 --> 00:28:54.400
 0 and you know, this Mac address

562
00:28:54.400 --> 00:28:58.100
 belongs to the router.

563
00:28:59.100 --> 00:29:00.300
You can see in here.

564
00:29:01.100 --> 00:29:05.500
Smack address belongs to the rotor. So it

565
00:29:04.500 --> 00:29:08.500
 means that Kylie sends

566
00:29:07.500 --> 00:29:11.100
 a reply ARP reply

567
00:29:10.100 --> 00:29:13.500
 packet ARP reply message

568
00:29:13.500 --> 00:29:15.200
 to the router.

569
00:29:16.300 --> 00:29:19.600
And what he says in his reply message.

570
00:29:19.600 --> 00:29:25.200
 He says that 2.15 the

571
00:29:23.200 --> 00:29:26.900
 IP address ends with

572
00:29:26.900 --> 00:29:29.600
 two dot 15 is at

573
00:29:29.600 --> 00:29:32.900
 my Mac

574
00:29:32.900 --> 00:29:32.900
 address.

575
00:29:33.800 --> 00:29:36.300
Is that color is mechanics?

576
00:29:37.500 --> 00:29:40.900
It says that the IP address and

577
00:29:40.900 --> 00:29:43.300
 sweet 2.15 belongs to

578
00:29:43.300 --> 00:29:43.500
 me.

579
00:29:44.700 --> 00:29:44.900
and

580
00:29:46.600 --> 00:29:47.300
In this way.

581
00:29:49.500 --> 00:29:54.000
This is again a direct ARP reply

582
00:29:53.400 --> 00:29:57.000
 packet. So it says to the router it says

583
00:29:56.100 --> 00:29:59.500
 to the router. I am the Windows

584
00:29:59.500 --> 00:30:02.800
 machine and it sends these messages over

585
00:30:02.800 --> 00:30:05.000
 and over again. You can see that.

586
00:30:05.800 --> 00:30:08.300
These message can be

587
00:30:08.300 --> 00:30:08.800
 seen.

588
00:30:09.500 --> 00:30:13.900
Again, so this phase was the ARP poison

589
00:30:13.900 --> 00:30:17.400
 and they are people things and after

590
00:30:17.400 --> 00:30:21.600
 this step after this step and the

591
00:30:20.600 --> 00:30:24.000
 router will think Cali is

592
00:30:23.000 --> 00:30:24.300
 Windows.

593
00:30:25.200 --> 00:30:28.600
And windows also will think Cali is

594
00:30:28.600 --> 00:30:29.400
 rotor.

595
00:30:30.100 --> 00:30:34.300
So now let's look at the traffic after ARP poisoning

596
00:30:33.300 --> 00:30:36.600
 part and let's look

597
00:30:36.600 --> 00:30:39.900
 at first packet after ARP poison.

598
00:30:40.800 --> 00:30:42.500
the an application data

599
00:30:43.900 --> 00:30:46.500
a packet goes from the

600
00:30:46.500 --> 00:30:51.000
 IP address 2.15 that

601
00:30:49.200 --> 00:30:53.200
 we know the windows

602
00:30:52.200 --> 00:30:56.100
 as the Windows machine and

603
00:30:55.100 --> 00:30:58.400
 to the IP address

604
00:30:58.400 --> 00:31:01.700
 and Suite one twenty and

605
00:31:01.700 --> 00:31:03.500
 151.

606
00:31:04.100 --> 00:31:08.200
When we look at the packet details, we see

607
00:31:07.200 --> 00:31:09.200
 that Mac address.

608
00:31:10.600 --> 00:31:13.900
Associated with this IP address is

609
00:31:13.900 --> 00:31:16.800
 76 and

610
00:31:16.800 --> 00:31:17.700
 B6.

611
00:31:18.500 --> 00:31:20.700
So let's look at the topology.

612
00:31:21.500 --> 00:31:24.800
As you see this Mac address belongs to

613
00:31:24.800 --> 00:31:28.000
 Windows. So in this line

614
00:31:27.800 --> 00:31:30.700
 a packet goes from

615
00:31:30.700 --> 00:31:34.400
 the Windows machine to this IP

616
00:31:33.400 --> 00:31:36.300
 address in a normal

617
00:31:36.300 --> 00:31:40.100
 in the normal terms the packets

618
00:31:39.100 --> 00:31:43.700
 sourcing from the windows will

619
00:31:42.700 --> 00:31:44.900
 go to the router.

620
00:31:47.400 --> 00:31:50.300
To forward the IP address in the

621
00:31:50.300 --> 00:31:53.000
 internet, but when we look at

622
00:31:53.300 --> 00:31:56.500
 the details, we can

623
00:31:56.500 --> 00:32:00.500
 see that the packet sort the

624
00:32:00.500 --> 00:32:03.800
 packet sourcing from the windows goes to

625
00:32:03.800 --> 00:32:06.800
 the this Mac address and this

626
00:32:06.800 --> 00:32:09.400
 Mac address doesn't belong to

627
00:32:09.400 --> 00:32:11.000
 the router.

628
00:32:12.300 --> 00:32:16.300
Because the MAC address and sweet 64

629
00:32:15.300 --> 00:32:18.400
 and 11 belongs to

630
00:32:18.400 --> 00:32:19.800
 Cali.

631
00:32:20.300 --> 00:32:24.800
So the packet comes from

632
00:32:24.800 --> 00:32:27.800
 the windows are going

633
00:32:27.800 --> 00:32:29.400
 to the Kali machine.

634
00:32:31.700 --> 00:32:34.700
Not not going to the water.

635
00:32:35.500 --> 00:32:35.700
so

636
00:32:36.700 --> 00:32:39.900
we can see the ARP poisoning

637
00:32:39.900 --> 00:32:41.000
 in this line.

638
00:32:42.400 --> 00:32:43.400
and now

639
00:32:44.700 --> 00:32:47.600
If we consider on

640
00:32:47.600 --> 00:32:48.500
 this packet.

641
00:32:49.100 --> 00:32:52.800
We can visualize this situation like

642
00:32:52.800 --> 00:32:53.100
 this.

643
00:32:54.500 --> 00:32:54.900
a packet

644
00:32:56.100 --> 00:32:59.400
goes from Windows to the internet.

645
00:33:00.300 --> 00:33:00.900
and

646
00:33:01.800 --> 00:33:04.900
you know that in the normal terms

647
00:33:04.900 --> 00:33:07.800
 under normal terms this packet

648
00:33:07.800 --> 00:33:09.800
 should go to the rotor.

649
00:33:10.200 --> 00:33:14.400
But in our situation the packet comes

650
00:33:13.400 --> 00:33:16.600
 from Windows are going

651
00:33:16.600 --> 00:33:18.500
 to cut a machine.

652
00:33:19.100 --> 00:33:23.200
and because after the Erp

653
00:33:22.200 --> 00:33:26.600
 poisoning Windows things that

654
00:33:26.600 --> 00:33:29.400
 the IP address of

655
00:33:29.400 --> 00:33:33.500
 the rotor belongs to the belongs to

656
00:33:33.500 --> 00:33:36.700
 this Mac address and it sends

657
00:33:36.700 --> 00:33:38.700
 the packet to the Cali

658
00:33:40.700 --> 00:33:41.100
so

659
00:33:43.300 --> 00:33:47.400
the packet is now on our calcium machine.

660
00:33:48.400 --> 00:33:49.500
in this step

661
00:33:51.900 --> 00:33:54.800
In the next packet we can see a

662
00:33:54.800 --> 00:33:57.200
 TCP routines mission.

663
00:33:57.800 --> 00:34:00.500
However, here we see that the same

664
00:34:00.500 --> 00:34:03.400
 packet was sent to the

665
00:34:03.400 --> 00:34:08.300
 same destination by Kali.

666
00:34:10.200 --> 00:34:12.100
with the IP address of windows

667
00:34:12.900 --> 00:34:15.600
So let's look at we see

668
00:34:15.600 --> 00:34:18.900
 in the packet details the source

669
00:34:18.900 --> 00:34:19.900
 IP address.

670
00:34:22.500 --> 00:34:24.300
belongs to the windows

671
00:34:26.800 --> 00:34:27.800
as the MAC address

672
00:34:29.900 --> 00:34:31.100
of Kali machine

673
00:34:31.800 --> 00:34:35.300
you can see the IP address of windows, but when

674
00:34:34.300 --> 00:34:37.300
 we look at the details, we can see the

675
00:34:37.300 --> 00:34:42.500
 MAC address of the Kali. So who sends

676
00:34:41.500 --> 00:34:44.800
 the packet the same packet is

677
00:34:44.800 --> 00:34:48.800
 the Cali machine actually and you

678
00:34:48.800 --> 00:34:51.200
 can see the source Mac address

679
00:34:51.200 --> 00:34:54.500
 belongs to the Cali machine, but IP address

680
00:34:54.500 --> 00:34:57.300
 can be seen as the

681
00:34:57.300 --> 00:34:58.700
 windows IP address.

682
00:34:59.500 --> 00:35:03.500
So in in this situation actually

683
00:35:02.500 --> 00:35:05.800
 Kali sends the

684
00:35:05.800 --> 00:35:09.700
 same packet to the destination again,

685
00:35:08.700 --> 00:35:11.200
 what happens in

686
00:35:11.200 --> 00:35:11.800
 this step?

687
00:35:13.500 --> 00:35:16.800
Kali forwards the packet coming from

688
00:35:16.800 --> 00:35:19.700
 the Windows machine to the

689
00:35:19.700 --> 00:35:20.100
 router.

690
00:35:20.900 --> 00:35:24.300
We can see Kali Sands

691
00:35:23.300 --> 00:35:27.500
 packet to the router because the destination

692
00:35:27.500 --> 00:35:30.600
 Mac address belongs to the rotor.

693
00:35:31.100 --> 00:35:35.600
So as a result the packets sourcing from

694
00:35:35.600 --> 00:35:39.200
 the Kali now and going to

695
00:35:39.200 --> 00:35:40.400
 the rotor.

696
00:35:41.200 --> 00:35:43.400
So let's imagine on.

697
00:35:43.800 --> 00:35:46.700
Our topology The Last Action in the

698
00:35:46.700 --> 00:35:50.100
 last step. The packet came

699
00:35:49.100 --> 00:35:52.600
 from the windows is in

700
00:35:52.600 --> 00:35:56.000
 here on the Cali machine now in the

701
00:35:55.700 --> 00:35:59.700
 next packet Kali recent and

702
00:35:59.700 --> 00:36:02.300
 or forward the packet to

703
00:36:02.300 --> 00:36:03.000
 the rotor.

704
00:36:03.600 --> 00:36:06.900
So in this packet, you can

705
00:36:06.900 --> 00:36:08.700
 see the IP address as

706
00:36:09.500 --> 00:36:12.600
2.15 but the MAC

707
00:36:12.600 --> 00:36:15.000
 address is the cutting machine.

708
00:36:15.700 --> 00:36:20.300
So Source, IP address is 2.15.

709
00:36:21.400 --> 00:36:22.300
but the MAC address

710
00:36:23.500 --> 00:36:24.500
is

711
00:36:27.300 --> 00:36:30.700
Mac address is 64 and

712
00:36:30.700 --> 00:36:33.500
 11. So the cutting calories

713
00:36:33.500 --> 00:36:36.100
 because the router knows that

714
00:36:36.100 --> 00:36:39.400
 the IP address belongs to

715
00:36:39.400 --> 00:36:41.600
 the this Mac address.

716
00:36:42.500 --> 00:36:45.200
So you so we are

717
00:36:45.200 --> 00:36:49.000
 we are seeing that in the packet The

718
00:36:48.400 --> 00:36:53.200
 Source IP address. Is this anti-source

719
00:36:51.200 --> 00:36:54.400
 Mac address is this

720
00:36:56.300 --> 00:36:59.300
So that is ARP poisoning or

721
00:36:59.300 --> 00:37:00.800
 mitm attack.

722
00:37:01.800 --> 00:37:05.000
So you can also detect ARP poisoning

723
00:37:04.600 --> 00:37:08.000
 attacks by examining fire shares

724
00:37:07.600 --> 00:37:11.000
 a duplicate IP address detected

725
00:37:10.300 --> 00:37:13.800
 running message, so you can see the

726
00:37:13.800 --> 00:37:17.500
 message as duplicate IP

727
00:37:16.500 --> 00:37:18.600
 address detected for

728
00:37:21.200 --> 00:37:25.000
Or this IP address and Mac address and you

729
00:37:24.200 --> 00:37:28.300
 can investigate these messages as

730
00:37:27.300 --> 00:37:30.600
 well. So you can also see such

731
00:37:30.600 --> 00:37:35.800
 warnings by going to the expert information under

732
00:37:33.800 --> 00:37:36.800
 the analyze

733
00:37:36.800 --> 00:37:38.700
 menu and expert.

734
00:37:40.600 --> 00:37:43.100
information window you can see

735
00:37:43.100 --> 00:37:44.800
 These Warnings

736
00:37:46.200 --> 00:37:50.900
so you can investigate the duplicate IP

737
00:37:50.900 --> 00:37:54.400
 address configured warnings in

738
00:37:53.400 --> 00:37:56.500
 here. This is

739
00:37:56.500 --> 00:37:59.700
 also useful to detect the

740
00:37:59.700 --> 00:38:02.800
 some ARP poison illustrations

741
00:38:02.800 --> 00:38:07.200
 or another malicious

742
00:38:05.200 --> 00:38:07.800
 activities.

743
00:38:09.400 --> 00:38:12.700
And that's it about ARP poisoning

744
00:38:12.700 --> 00:38:13.200
 now.

745
00:38:14.700 --> 00:38:17.300
Let's look at the example of

746
00:38:17.300 --> 00:38:21.000
 an another attack type about

747
00:38:20.200 --> 00:38:23.200
 the ARP. Let's look at

748
00:38:23.200 --> 00:38:26.800
 the example of an ARP storm attack so

749
00:38:26.800 --> 00:38:29.400
 we can close this PK file

750
00:38:29.400 --> 00:38:29.700
 now.

751
00:38:31.800 --> 00:38:35.200
It is an attack type intentionally, correct

752
00:38:34.200 --> 00:38:37.200
 by an attacker from within the

753
00:38:37.200 --> 00:38:41.800
 local network as well in Erp in

754
00:38:40.800 --> 00:38:43.600
 Erp packet storm. The

755
00:38:43.600 --> 00:38:47.100
 attacker keeps generating broadcasts.

756
00:38:48.600 --> 00:38:51.400
The over and over again and in the

757
00:38:51.400 --> 00:38:54.000
 end it may render the network unable to

758
00:38:54.900 --> 00:38:55.400
 carry normal traffic.

759
00:38:55.900 --> 00:38:59.200
That is it can consume all network

760
00:38:58.200 --> 00:39:02.600
 resources that are normal sufficient and

761
00:39:01.600 --> 00:39:04.500
 IRP and ARP storm

762
00:39:04.500 --> 00:39:08.500
 also known as an ARP fluid is

763
00:39:07.500 --> 00:39:11.100
 a type of Cyber attack that involves

764
00:39:10.100 --> 00:39:13.300
 sanding a large number

765
00:39:13.300 --> 00:39:16.300
 of ARP messages to a

766
00:39:16.300 --> 00:39:19.200
 device or network in an attempt to

767
00:39:19.200 --> 00:39:22.100
 overwhelm to overwhelm it.

768
00:39:22.100 --> 00:39:25.600
 So the goal of an Erp storm

769
00:39:25.600 --> 00:39:28.700
 attack is to disrupt communication and

770
00:39:28.700 --> 00:39:31.500
 potentially cause a denial

771
00:39:31.500 --> 00:39:35.300
 of service as you know deals attack or

772
00:39:34.300 --> 00:39:38.500
 those those attack by

773
00:39:37.500 --> 00:39:40.400
 overall meaning the target

774
00:39:40.400 --> 00:39:44.200
 with unnecessary terrific. So

775
00:39:43.200 --> 00:39:46.400
 in an ARP storm attack,

776
00:39:46.400 --> 00:39:49.300
 the attacker may send a large

777
00:39:49.300 --> 00:39:52.600
 number of ARP requests or

778
00:39:52.600 --> 00:39:55.600
 replies to do Target devices or

779
00:39:55.900 --> 00:39:58.700
it using either a single Source

780
00:39:58.700 --> 00:40:01.700
 or multiple sources the target

781
00:40:01.700 --> 00:40:04.800
 May then become overwhelmed with

782
00:40:04.800 --> 00:40:08.200
 the volume of traffic and be

783
00:40:07.200 --> 00:40:10.300
 unable to process legitimate.

784
00:40:11.100 --> 00:40:15.100
To process legitimate requests disrupting

785
00:40:14.100 --> 00:40:19.500
 communication and potentially causing dios.

786
00:40:17.500 --> 00:40:21.000
 So ARP

787
00:40:20.200 --> 00:40:23.200
 storm attacks can be difficult

788
00:40:23.200 --> 00:40:26.900
 to detect and prevent as

789
00:40:26.900 --> 00:40:29.600
 the ARP protocol is essential for

790
00:40:29.600 --> 00:40:33.100
 communication on a local area network

791
00:40:32.100 --> 00:40:36.300
 and it is difficult to distinguish

792
00:40:35.300 --> 00:40:38.600
 between legitimate and

793
00:40:38.600 --> 00:40:41.200
 malicious traffic. So however, there

794
00:40:41.200 --> 00:40:45.900
 are measures that can be to mitigate the

795
00:40:45.900 --> 00:40:48.800
 risk of such attacks

796
00:40:48.800 --> 00:40:52.000
 such as implementing rate limiting

797
00:40:51.200 --> 00:40:54.500
 and filtering rules and using

798
00:40:54.500 --> 00:40:57.500
 Arps to proofing detection tools. Also,

799
00:40:57.500 --> 00:41:00.300
 maybe let's look at an

800
00:41:00.300 --> 00:41:03.600
 example of ARP storm in here

801
00:41:03.600 --> 00:41:07.000
 at first glance. We notize

802
00:41:06.100 --> 00:41:09.400
 that between 0 and

803
00:41:11.800 --> 00:41:14.600
one second more than

804
00:41:14.600 --> 00:41:18.400
 you can see between second zero

805
00:41:17.400 --> 00:41:20.500
 and the second one.

806
00:41:22.300 --> 00:41:23.600
in this range

807
00:41:25.200 --> 00:41:28.700
we can see we can notice more than

808
00:41:28.700 --> 00:41:31.500
 20 ARP broadcast

809
00:41:31.500 --> 00:41:32.700
 packets.

810
00:41:33.300 --> 00:41:34.100
You can see.

811
00:41:35.400 --> 00:41:39.000
These are the ARP broadcast packets.

812
00:41:40.100 --> 00:41:40.300
and

813
00:41:42.400 --> 00:41:45.300
this is definitely not normal in the

814
00:41:45.300 --> 00:41:46.200
 next seconds.

815
00:41:46.900 --> 00:41:47.900
in the next seconds

816
00:41:49.200 --> 00:41:54.200
about 70 broadcast packets

817
00:41:52.200 --> 00:41:55.400
 continue to be set.

818
00:41:56.200 --> 00:41:59.700
This is an example of Erp store

819
00:41:59.700 --> 00:42:00.500
 attack.

820
00:42:01.500 --> 00:42:04.900
So this is an example of ARP storm

821
00:42:04.900 --> 00:42:07.200
 attack, and that's all.

822
00:42:10.600 --> 00:42:13.100
So that's all for now. See you on the

823
00:42:13.100 --> 00:42:13.500
 next video.
