WEBVTT - This file was automatically generated by VIMEO

1
00:00:07.400 --> 00:00:10.600
 Hello guys and welcome to another video of this chapter.

2
00:00:10.200 --> 00:00:13.200
 So this video will help you

3
00:00:13.200 --> 00:00:16.500
 understand, icmp flow the tags, otherwise

4
00:00:16.500 --> 00:00:19.300
 known as Smurf attacks. Of course, we are going

5
00:00:19.300 --> 00:00:23.300
 to show you how to perform such an attack using

6
00:00:22.300 --> 00:00:25.200
 Kali Linux and how you

7
00:00:25.200 --> 00:00:28.700
 can precisely identify one

8
00:00:28.700 --> 00:00:29.800
 of these type of a

9
00:00:30.100 --> 00:00:34.000
 Likes using Wireshark Smurf,

10
00:00:33.500 --> 00:00:37.500
 attacks have the potential to be devastating,

11
00:00:36.200 --> 00:00:39.600
 both to the victim network.

12
00:00:39.600 --> 00:00:42.100
 And to the Network's used to uplift by the

13
00:00:42.100 --> 00:00:46.100
 attack, which we are going to explain later on how it

14
00:00:45.100 --> 00:00:48.800
 works. And I didn't

15
00:00:48.800 --> 00:00:51.800
 control message. Protocol Smurf, attack is

16
00:00:51.800 --> 00:00:54.400
 a Brute Force attack on the date. Broadcast feature.

17
00:00:54.400 --> 00:00:55.500
 That is built.

18
00:00:56.400 --> 00:00:58.100
 Into the IP protocol.

19
00:00:59.300 --> 00:01:01.300
 So, this type of attacks?

20
00:01:01.500 --> 00:01:04.800
 I can easily take Atmos by surprise

21
00:01:04.800 --> 00:01:07.100
 and can become challenging to identify.

22
00:01:09.200 --> 00:01:12.800
 Luckily, the tools like Wireshark that makes it easier

23
00:01:12.800 --> 00:01:15.400
 to capture and verify such

24
00:01:15.400 --> 00:01:18.400
 suspicions of any type of denial of

25
00:01:18.400 --> 00:01:21.300
 service attacks. So how is

26
00:01:21.300 --> 00:01:24.700
 MP float? The tax work. A Smurf attack

27
00:01:24.800 --> 00:01:28.000
 is not so terribly sophisticated. It's

28
00:01:27.300 --> 00:01:30.600
 just a matter of routing and letting

29
00:01:30.600 --> 00:01:32.000
 IP take its course.

30
00:01:34.200 --> 00:01:37.200
 Usually unfolds in some simple steps that

31
00:01:37.200 --> 00:01:40.600
 we're going to go through now. So the hiker

32
00:01:40.600 --> 00:01:43.900
 firstly identifies a victim IP address

33
00:01:43.100 --> 00:01:46.500
 with usually the web

34
00:01:46.500 --> 00:01:49.200
 server after that hike, it

35
00:01:49.200 --> 00:01:53.000
 tries to identify an intermediary site

36
00:01:52.100 --> 00:01:55.300
 that will help him or

37
00:01:55.300 --> 00:01:58.400
 here amplify the attack.

38
00:02:01.400 --> 00:02:05.500
 Then if I give starts to send a large amount of icmp

39
00:02:04.100 --> 00:02:07.300
 traffic at

40
00:02:07.300 --> 00:02:11.500
 the broadcast, address of the intermediary sides,

41
00:02:10.200 --> 00:02:13.300
 this bag is have the source

42
00:02:13.300 --> 00:02:17.000
 IP address both to point towards the victim. If

43
00:02:16.100 --> 00:02:20.200
 the mediator is delivered broadcast at

44
00:02:20.700 --> 00:02:23.600
 layer 2 to all the holes on the

45
00:02:23.600 --> 00:02:26.100
 subnet and the whole supplied the

46
00:02:26.100 --> 00:02:26.800
 victim Network.

47
00:02:27.700 --> 00:02:30.700
 So in this case, you might be wondering how

48
00:02:30.700 --> 00:02:33.400
 could a little ping traffic take

49
00:02:33.400 --> 00:02:36.600
 down the side. So take for instance that a

50
00:02:36.600 --> 00:02:40.100
 hiker has a cable modem and

51
00:02:39.500 --> 00:02:42.800
 since one Mega

52
00:02:42.800 --> 00:02:45.500
 BPS spoofed icmp stream at

53
00:02:45.900 --> 00:02:48.700
 a chosen intermediary site. So

54
00:02:48.700 --> 00:02:52.000
 let's suppose that this intermediary sides

55
00:02:51.600 --> 00:02:54.600
 have 150 horse that

56
00:02:54.700 --> 00:02:56.900
 can respond to that icmp.

57
00:02:57.200 --> 00:03:00.600
 Dream. So this means that the

58
00:03:00.600 --> 00:03:03.600
 intermediary sites can

59
00:03:03.600 --> 00:03:07.200
 amplify to 150 megabits PS attack

60
00:03:06.200 --> 00:03:09.600
 traveling from the appli fires towards

61
00:03:09.600 --> 00:03:12.400
 the victim. So this how you can keep this

62
00:03:12.400 --> 00:03:15.300
 up as long as he has a connection and as long as

63
00:03:15.300 --> 00:03:18.700
 of course the amplifiers continue to broadcast the icmp traffic and

64
00:03:18.700 --> 00:03:22.500
 as long as you could then use, of course this

65
00:03:22.500 --> 00:03:26.100
 traffic overwhelms, the victim resulting

66
00:03:25.100 --> 00:03:27.100
 in a denial of service.

67
00:03:27.300 --> 00:03:30.200
 Attack for the victim. So now we're going to

68
00:03:30.200 --> 00:03:33.900
 go ahead and see and perform such

69
00:03:33.900 --> 00:03:37.100
 an attack. Icmp flag attack with

70
00:03:36.100 --> 00:03:40.600
 Kali Linux. So we are going to use ATP, 3

71
00:03:40.900 --> 00:03:43.700
 on Kali Linux. And of course, our Target machine

72
00:03:43.700 --> 00:03:46.900
 will be a Windows machine. With

73
00:03:46.900 --> 00:03:49.800
 we're going to load Wireshark

74
00:03:49.800 --> 00:03:52.500
 the in order to capture this

75
00:03:52.500 --> 00:03:55.400
 type of Smurf, attack on our Windows

76
00:03:55.400 --> 00:03:57.100
 machine and see I'm

77
00:03:57.200 --> 00:04:01.400
 Go through the results of Wireshark and

78
00:04:01.400 --> 00:04:05.400
 just explore how Wireshark captured the

79
00:04:05.400 --> 00:04:06.100
 traffic.

80
00:04:07.200 --> 00:04:11.000
 So here back to our Linux machine Kali

81
00:04:10.300 --> 00:04:13.200
 Linux machine, we're going to open a

82
00:04:13.200 --> 00:04:16.100
 command line. Make sure you're always roots or you

83
00:04:16.100 --> 00:04:19.700
 can also use a pseudo if you want. So the command

84
00:04:19.100 --> 00:04:22.500
 is already laid

85
00:04:22.500 --> 00:04:25.500
 out and I have it here which

86
00:04:25.500 --> 00:04:28.400
 I am going to explain how everything

87
00:04:28.400 --> 00:04:31.100
 works. What is the syntax of the command? So you

88
00:04:31.100 --> 00:04:34.500
 start with shoe. Do you type h pink, three?

89
00:04:35.700 --> 00:04:40.000
 You can also use H pink three space

90
00:04:39.100 --> 00:04:42.200
 Dash does help, so you can find all

91
00:04:42.200 --> 00:04:45.100
 sorts of things that this command includes and

92
00:04:45.100 --> 00:04:48.600
 what you can do with it. So in this type of

93
00:04:48.600 --> 00:04:51.600
 lesson, we're going to learn how to flag a

94
00:04:51.600 --> 00:04:54.900
 target with icmp stream. So

95
00:04:54.900 --> 00:04:57.500
 that means and we are going to use icmp as

96
00:04:57.500 --> 00:05:00.300
 a protocol. That's does icmp. And

97
00:05:00.300 --> 00:05:04.200
 then space we're going to choose. Then the type of

98
00:05:05.400 --> 00:05:09.300
 Attack we won, which is flood. There's the flood and

99
00:05:09.300 --> 00:05:12.400
 then space does a which means that it's going to be

100
00:05:12.700 --> 00:05:16.100
 spoofing, our address 192

101
00:05:15.100 --> 00:05:18.500
 168 8.16 for

102
00:05:18.500 --> 00:05:21.200
 is our victims address.

103
00:05:22.300 --> 00:05:25.700
 In this case, as I told you before, we would be a Windows machine.

104
00:05:25.900 --> 00:05:28.400
 And then you have to go ahead and type another

105
00:05:28.400 --> 00:05:32.200
 IP address, which is basically your network range,

106
00:05:31.200 --> 00:05:34.700
 which you want to amplify

107
00:05:34.300 --> 00:05:35.800
 the

108
00:05:37.400 --> 00:05:40.500
 Stream. So before we go ahead

109
00:05:40.500 --> 00:05:43.400
 and hit enter. We need to go back to our

110
00:05:43.600 --> 00:05:46.900
 Windows machine fire up, Wireshark

111
00:05:46.100 --> 00:05:49.200
 start capturing the traffic and then we hit the

112
00:05:49.200 --> 00:05:52.800
 command. So we fired up Wireshark

113
00:05:52.900 --> 00:05:55.500
 in our Windows machine. We

114
00:05:55.500 --> 00:05:58.700
 need to select our interface. We

115
00:05:58.700 --> 00:06:01.700
 can select a network interface that

116
00:06:01.700 --> 00:06:05.000
 we can select start capturing, hit

117
00:06:04.000 --> 00:06:05.700
 capture.

118
00:06:06.300 --> 00:06:09.300
 Start capturing packets, and why

119
00:06:09.300 --> 00:06:12.800
 should we start capturing your traffic that

120
00:06:12.800 --> 00:06:15.600
 is generated now on your windows messy.

121
00:06:15.800 --> 00:06:19.000
 So let's just go back on Kali, Linux, hit

122
00:06:18.600 --> 00:06:21.800
 enter on H pink, three, command,

123
00:06:21.800 --> 00:06:24.300
 and then come back here and see if something

124
00:06:24.300 --> 00:06:24.900
 happens.

125
00:06:26.200 --> 00:06:29.400
 So back to a Linux machine, we are ready to hit enter

126
00:06:29.400 --> 00:06:32.100
 here and lock the attack and

127
00:06:32.100 --> 00:06:36.000
 then we immediately going to turn back to Windows

128
00:06:35.300 --> 00:06:38.500
 machine and check

129
00:06:38.500 --> 00:06:41.500
 if Wireshark can catch this type of attack

130
00:06:41.500 --> 00:06:44.000
 and what is happening. So let's just hit enter.

131
00:06:47.100 --> 00:06:50.100
 So let's just hit enter and you can see that the

132
00:06:50.100 --> 00:06:53.900
 attack is starting. Let's go back to Windows machine

133
00:06:53.900 --> 00:06:56.300
 and check wire circuit. If it

134
00:06:56.300 --> 00:06:59.100
 started capturing the traffic. So back in

135
00:06:59.100 --> 00:07:02.100
 our Windows machine, you can see that why I

136
00:07:02.100 --> 00:07:04.500
 said it's already starting capturing.

137
00:07:06.600 --> 00:07:09.100
 The icmp packets.

138
00:07:10.300 --> 00:07:13.200
 Coming straight, you can see there is a continuous stream.

139
00:07:15.300 --> 00:07:16.800
 Happening all the time.

140
00:07:20.500 --> 00:07:23.100
 And I can keep this attack up. As long as I

141
00:07:23.100 --> 00:07:27.100
 want it. I can use like intermediary sides.

142
00:07:28.200 --> 00:07:31.300
 With more holes that we can amplify my S MB.

143
00:07:33.700 --> 00:07:36.300
 Stream, you can see the

144
00:07:36.300 --> 00:07:39.600
 attack is going on. So let's just go back to

145
00:07:39.700 --> 00:07:42.900
 Kali Linux machine, stopped the attack and

146
00:07:42.900 --> 00:07:44.500
 come back here. And

147
00:07:46.600 --> 00:07:49.900
 Take a deeper look on the captured

148
00:07:49.200 --> 00:07:52.700
 traffic so you can stop

149
00:07:52.700 --> 00:07:56.500
 the attack by hitting Pedrosa, just

150
00:07:56.500 --> 00:07:59.400
 stops the attack and then we can go back to our Windows

151
00:07:59.400 --> 00:08:02.400
 machine and see what is happening on

152
00:08:02.400 --> 00:08:05.800
 wires check. So as you can see where

153
00:08:05.800 --> 00:08:08.700
 I went back to capture in normal traffic.

154
00:08:10.200 --> 00:08:13.700
 and we can just go ahead and stop the capturing and

155
00:08:14.800 --> 00:08:17.900
 You can just go ahead and review this. You

156
00:08:17.900 --> 00:08:20.200
 can just go ahead and save the

157
00:08:20.200 --> 00:08:23.400
 results by going to file save as your

158
00:08:23.400 --> 00:08:26.300
 white sock, if you want to keep this traffic and you

159
00:08:26.300 --> 00:08:29.600
 can see that when before we start the attack, the

160
00:08:29.800 --> 00:08:32.700
 Wireshark started, capturing normal traffic and

161
00:08:32.700 --> 00:08:35.400
 responses from our computer. Then

162
00:08:35.400 --> 00:08:37.800
 we hit the attack.

163
00:08:39.300 --> 00:08:42.600
 Now, Kali Linux machine and all

164
00:08:42.600 --> 00:08:43.400
 of a sudden.

165
00:08:45.400 --> 00:08:48.700
 Huge flood of icmp packets started hitting our

166
00:08:48.700 --> 00:08:52.900
 Windows machine continuously. You

167
00:08:52.900 --> 00:08:56.800
 can see the source IP, which is Windows

168
00:08:56.800 --> 00:09:00.500
 AP and our Network range.

169
00:09:03.100 --> 00:09:03.600
 Here.

170
00:09:05.700 --> 00:09:08.000
 Do you see this will go on forever?

171
00:09:09.200 --> 00:09:10.800
 You can leave it if you want.

172
00:09:11.800 --> 00:09:15.100
 So what was covered in this lesson is

173
00:09:14.100 --> 00:09:18.900
 that we basically learned

174
00:09:17.400 --> 00:09:20.800
 how icmp flood

175
00:09:20.500 --> 00:09:23.800
 attacks work. We learned how

176
00:09:23.800 --> 00:09:28.100
 to perform one on Kali Linux and

177
00:09:27.100 --> 00:09:31.300
 of course how to correctly, identify

178
00:09:30.500 --> 00:09:33.500
 such an attack on our,

179
00:09:33.300 --> 00:09:36.700
 in this case with those my seam by

180
00:09:36.700 --> 00:09:39.200
 using Wireshark. Thank you guys for

181
00:09:39.200 --> 00:09:41.400
 this lesson and you can just go ahead.

182
00:09:41.500 --> 00:09:44.900
 Ed and click on the next video which is detecting Mark

183
00:09:44.900 --> 00:09:45.400
 flooding.
