WEBVTT - This file was automatically generated by VIMEO

0
00:00:06.300 --> 00:00:09.100
Okay, guys, welcome to the first

1
00:00:09.100 --> 00:00:12.400
 demo in this course probably you have been waiting

2
00:00:12.400 --> 00:00:15.500
 for a long time for the first demo and now it's

3
00:00:15.500 --> 00:00:18.700
 time to present it to you. And the

4
00:00:18.700 --> 00:00:21.600
 first demo is gonna be about burps with

5
00:00:21.600 --> 00:00:24.300
 Intruder how to use burp Suite Intruder

6
00:00:24.300 --> 00:00:27.700
 in practice and how to use it for fuzzing in

7
00:00:27.700 --> 00:00:30.500
 the context of SQL injection. So

8
00:00:30.500 --> 00:00:34.000
 I'm going to do here fuzzing for SQL

9
00:00:33.300 --> 00:00:36.400
 injection with burp sweet Intruder, okay.

10
00:00:37.300 --> 00:00:37.900
So let's start.

11
00:00:38.700 --> 00:00:41.300
I've got a testing web application. This is

12
00:00:41.300 --> 00:00:44.500
 actually an online shopping platform,

13
00:00:44.500 --> 00:00:47.100
 and I've got some sellers here.

14
00:00:47.800 --> 00:00:50.500
free sellers David Cooper and

15
00:00:50.500 --> 00:00:52.600
 Michael green and Mark Ross

16
00:00:53.300 --> 00:00:56.400
and I can hear do some searching by

17
00:00:56.400 --> 00:00:57.000
 name.

18
00:00:57.700 --> 00:01:00.100
So I can put for example at David here.

19
00:01:01.100 --> 00:01:04.500
I can search if there is David and indeed

20
00:01:04.500 --> 00:01:08.500
 there is David Cooper, right and whatever I'm

21
00:01:08.500 --> 00:01:12.200
 trying to search for it is sent in

22
00:01:11.200 --> 00:01:15.200
 the get parameter named search name,

23
00:01:14.200 --> 00:01:17.400
 right? So you see the parameter search

24
00:01:17.400 --> 00:01:20.700
 name and the value is right now David now, let

25
00:01:20.700 --> 00:01:23.500
 me provide something random right if I provide something

26
00:01:23.500 --> 00:01:25.800
 random then there is no seller like this.

27
00:01:26.800 --> 00:01:29.300
And I see the message. We can't find

28
00:01:29.300 --> 00:01:32.300
 any seller that matches search criteria. Well, this

29
00:01:32.300 --> 00:01:35.500
 is expected because I provided some random characters,

30
00:01:35.500 --> 00:01:36.000
 okay.

31
00:01:36.900 --> 00:01:37.900
Let me go back.

32
00:01:39.600 --> 00:01:42.900
To sellers.php right now.

33
00:01:42.900 --> 00:01:45.700
 We've got this free free Sellers

34
00:01:45.700 --> 00:01:48.900
 and now I kind of you know thinking about

35
00:01:48.900 --> 00:01:52.100
 the story here. We've got some sellers

36
00:01:51.100 --> 00:01:54.900
 we've got some search functionality

37
00:01:54.900 --> 00:01:57.500
 and most probably this sellers are

38
00:01:57.500 --> 00:02:00.300
 stored in the database, right? This is how it looks

39
00:02:00.300 --> 00:02:03.400
 like in modern web applications and there is the

40
00:02:03.400 --> 00:02:06.400
 kind of database processing. So maybe I can

41
00:02:06.400 --> 00:02:09.800
 provide here some malicious payload and

42
00:02:09.800 --> 00:02:13.200
 maybe I am able to do SQL injection here. Who

43
00:02:12.200 --> 00:02:15.400
 knows let's check if this is

44
00:02:15.400 --> 00:02:16.500
 possible.

45
00:02:17.300 --> 00:02:21.200
And now I'm gonna show you how to use

46
00:02:20.200 --> 00:02:23.600
 fuzzing to check whether an SQL

47
00:02:23.600 --> 00:02:26.400
 injection here is possible or not. Okay.

48
00:02:27.200 --> 00:02:30.700
So the first thing that I have to do is I

49
00:02:30.700 --> 00:02:33.500
 have to an intercept the

50
00:02:33.500 --> 00:02:36.600
 request going out from my browser. That's the

51
00:02:36.600 --> 00:02:39.200
 first thing that I'm gonna do and keep in

52
00:02:39.200 --> 00:02:42.800
 mind that we are here in the world of web application

53
00:02:42.800 --> 00:02:45.900
 security testing. So it's all about requests and

54
00:02:45.900 --> 00:02:48.200
 responses and when you want to do

55
00:02:48.200 --> 00:02:51.500
 fuzzing, then you need to have a request right?

56
00:02:51.500 --> 00:02:54.800
 So I'm gonna first intercept the

57
00:02:54.800 --> 00:02:57.200
 request going out from my browser and then

58
00:02:57.200 --> 00:03:00.400
 I'm gonna send this request to Intruder but step by step

59
00:03:00.400 --> 00:03:03.600
 first. I'm going to generate the request.

60
00:03:04.400 --> 00:03:07.200
From my browser and I'm going to intercept it.

61
00:03:07.800 --> 00:03:10.200
What I've got here in my testing web application is

62
00:03:10.200 --> 00:03:13.100
 burp Suite free edition.

63
00:03:14.200 --> 00:03:17.600
And one part of burp a

64
00:03:17.600 --> 00:03:20.500
 sweet free edition is proxy what you

65
00:03:20.500 --> 00:03:24.100
 can see in the upper left corner and there

66
00:03:23.100 --> 00:03:26.200
 is the so-called Interceptor here.

67
00:03:26.200 --> 00:03:29.700
 And now I'm going to turn on

68
00:03:29.700 --> 00:03:33.800
 the Interceptor because I'm going to intercept

69
00:03:32.800 --> 00:03:35.300
 the request going out from

70
00:03:35.300 --> 00:03:38.500
 my browser and in my testing environment the traffic

71
00:03:38.500 --> 00:03:41.500
 going out from my browser is sent out through the proxy. So

72
00:03:41.500 --> 00:03:44.800
 if I turn on the Interceptor here, I'm

73
00:03:44.800 --> 00:03:47.300
 going to intercept outgoing requests. Okay. So this

74
00:03:47.300 --> 00:03:50.600
 is how it looks like so I'm going to turn it on now. I'm

75
00:03:50.600 --> 00:03:52.200
 going to go to my web application.

76
00:03:53.300 --> 00:03:56.500
And in the search name I will provide again something arbitrary.

77
00:03:57.700 --> 00:03:59.100
and yeah search

78
00:03:59.700 --> 00:04:02.100
now, let's go to my proxy.

79
00:04:03.300 --> 00:04:06.200
And here you can see that indeed the request

80
00:04:06.200 --> 00:04:07.700
 has been intercepted you see.

81
00:04:08.800 --> 00:04:12.000
There is a surgeon in parameter with some

82
00:04:11.400 --> 00:04:13.100
 random value, right?

83
00:04:13.900 --> 00:04:16.300
Now this is this is

84
00:04:16.300 --> 00:04:19.200
 the proxy it has been intercepted now. I

85
00:04:19.200 --> 00:04:22.300
 need to send it to Intruder how

86
00:04:22.300 --> 00:04:22.600
 to do it.

87
00:04:23.500 --> 00:04:24.400
Click, right?

88
00:04:25.500 --> 00:04:28.500
And choose option send to intruder.

89
00:04:29.800 --> 00:04:32.500
Okay now let me go to intruder.

90
00:04:34.300 --> 00:04:37.100
and it is it is out there

91
00:04:37.100 --> 00:04:40.400
 go to positions and you see this is my request

92
00:04:40.400 --> 00:04:42.300
 right now it is

93
00:04:43.300 --> 00:04:46.200
You know in Intruder and this is what I wanted to

94
00:04:46.200 --> 00:04:46.900
 happen, okay?

95
00:04:48.100 --> 00:04:51.100
So let me know clear all this highlights.

96
00:04:52.300 --> 00:04:56.900
And let me show you how to instruct the

97
00:04:56.900 --> 00:04:59.400
 burp suit Intruder. Where is

98
00:04:59.400 --> 00:05:02.500
 my placeholder for malicious payloads? Okay.

99
00:05:03.200 --> 00:05:06.800
So and we are interested in the surge name parameter,

100
00:05:06.800 --> 00:05:09.800
 right? This is where we are sending our

101
00:05:09.800 --> 00:05:12.400
 data that we want to you know,

102
00:05:12.400 --> 00:05:15.400
 we want to find out whether a given seller

103
00:05:15.400 --> 00:05:16.800
 is available or not.

104
00:05:17.700 --> 00:05:20.300
And we are providing the data out there or

105
00:05:20.300 --> 00:05:23.200
 the data that we are providing is sent in

106
00:05:23.200 --> 00:05:26.500
 certainly parameter, right? So this is my placeholder for

107
00:05:26.500 --> 00:05:28.900
 malicious data, so I'm going to

108
00:05:30.500 --> 00:05:33.400
Highlight this one and once it

109
00:05:33.400 --> 00:05:33.900
 is highlighted.

110
00:05:36.200 --> 00:05:37.600
I'm gonna click add.

111
00:05:39.200 --> 00:05:39.600
and now

112
00:05:41.300 --> 00:05:45.100
This is a placeholder for my malicious payloads.

113
00:05:44.100 --> 00:05:45.200
 Okay?

114
00:05:46.100 --> 00:05:49.500
So now I instructed burp suit Intruder that

115
00:05:49.500 --> 00:05:52.200
 this is the placeholder for malicious payloads.

116
00:05:53.100 --> 00:05:53.200
cool

117
00:05:54.700 --> 00:05:57.500
And now you see the attack type

118
00:05:57.500 --> 00:06:01.000
 is sniper. This is what I explained

119
00:06:00.400 --> 00:06:04.300
 to you in the previous video.

120
00:06:03.300 --> 00:06:07.400
 So this is the most popular attack

121
00:06:06.400 --> 00:06:09.800
 type every single malicious

122
00:06:09.800 --> 00:06:13.300
 payload from the list is gonna be taken and put

123
00:06:12.300 --> 00:06:15.200
 into this placeholder.

124
00:06:15.900 --> 00:06:18.900
And yeah, this is an how

125
00:06:18.900 --> 00:06:23.000
 it works. So we also need and the

126
00:06:21.100 --> 00:06:24.800
 list of payloads right? So let

127
00:06:24.800 --> 00:06:26.400
 me go to the payloads here.

128
00:06:28.200 --> 00:06:31.700
And here you're gonna see payload options simple list

129
00:06:31.700 --> 00:06:34.200
 now. I'm gonna load the list

130
00:06:34.200 --> 00:06:35.000
 of payloads.

131
00:06:36.100 --> 00:06:39.800
And the list of payloads that I already introduced to

132
00:06:39.800 --> 00:06:43.500
 you in the previous video is here in

133
00:06:42.500 --> 00:06:45.800
 the root directory user share

134
00:06:45.800 --> 00:06:48.100
 W fast word list injections, right?

135
00:06:49.300 --> 00:06:52.200
And now I've got it open and you can

136
00:06:52.200 --> 00:06:52.400
 see.

137
00:06:53.800 --> 00:06:57.300
That there are different lists of payloads.

138
00:06:56.300 --> 00:06:59.500
 There are lists of payloads

139
00:06:59.500 --> 00:07:02.300
 for a sequel injection and here.

140
00:07:03.600 --> 00:07:05.600
here for path traversal

141
00:07:06.300 --> 00:07:09.700
and we've got also for XML access,

142
00:07:09.700 --> 00:07:12.800
 you know, quite many and different

143
00:07:12.800 --> 00:07:15.800
 lists, which is really nice because it

144
00:07:15.800 --> 00:07:18.200
 gives us an opportunity to do

145
00:07:18.200 --> 00:07:23.000
 fuzzing for different kinds of vulnerableties as

146
00:07:22.100 --> 00:07:25.200
 I mentioned at the very beginning of this demo. I'm gonna

147
00:07:25.200 --> 00:07:29.400
 focus on SQL injection because this is this is the context, you

148
00:07:28.400 --> 00:07:31.700
 know of this story and I'll

149
00:07:31.700 --> 00:07:32.300
 click open.

150
00:07:33.800 --> 00:07:36.800
So all this malicious payloads

151
00:07:36.800 --> 00:07:40.500
 have been let's say incorporated or

152
00:07:40.500 --> 00:07:43.800
 loaded to burps with Intruder. So what

153
00:07:43.800 --> 00:07:46.200
 I've got right now is I've got a list

154
00:07:46.200 --> 00:07:48.600
 of payloads already loaded.

155
00:07:49.700 --> 00:07:53.600
And here I've got my payload

156
00:07:52.600 --> 00:07:55.800
 position right? I clearly marked

157
00:07:55.800 --> 00:07:57.300
 that. This is a payload position.

158
00:07:58.500 --> 00:08:01.200
And the attack type is sniper, right? So it looks

159
00:08:01.200 --> 00:08:05.000
 like we've got everything now. Let me go to Intruder here.

160
00:08:04.800 --> 00:08:07.000
 Click Start attack, okay.

161
00:08:08.100 --> 00:08:11.500
And now what you can see here kind of pop-up message

162
00:08:11.500 --> 00:08:14.700
 the free edition of verb contains a

163
00:08:14.700 --> 00:08:16.600
 demo version of burp Suite intruder.

164
00:08:17.400 --> 00:08:20.100
Some functionality is disabled and attacks arm

165
00:08:20.100 --> 00:08:23.200
 time throttled. I will tell you something more about

166
00:08:23.200 --> 00:08:26.100
 this when the fuzzing is underway. So let me

167
00:08:26.100 --> 00:08:29.200
 click. Okay, and now I'm gonna tell you something

168
00:08:29.200 --> 00:08:29.700
 more about this.

169
00:08:30.400 --> 00:08:33.100
I'm using here the free addition of

170
00:08:33.100 --> 00:08:36.400
 perp Suite you can go you can take it as the

171
00:08:36.400 --> 00:08:39.700
 name suggests. It's just free. And when you

172
00:08:39.700 --> 00:08:42.600
 use free addition, then when the

173
00:08:42.600 --> 00:08:45.500
 time goes on then the speed

174
00:08:45.500 --> 00:08:48.100
 of fuzzing decreases, right? This is

175
00:08:48.100 --> 00:08:51.700
 how it works. So this fuzzing works perfectly

176
00:08:51.700 --> 00:08:54.600
 good in burp Suite free edition. But again when

177
00:08:54.600 --> 00:08:57.900
 the time goes on then the speed

178
00:08:57.900 --> 00:09:00.300
 of fuzzing decreases and when you

179
00:09:00.300 --> 00:09:03.900
 want to have you know, the maximum speed

180
00:09:03.900 --> 00:09:06.600
 of fuzzing then we've got a problem when

181
00:09:06.600 --> 00:09:09.400
 you've got a free addition of

182
00:09:09.400 --> 00:09:12.600
 purposefute. So if you want to have

183
00:09:12.600 --> 00:09:15.100
 a maximum speed of fuzzing, then you

184
00:09:15.100 --> 00:09:18.900
 just need to buy burp sweet Pro and I really

185
00:09:18.900 --> 00:09:21.500
 do recommend you to do it because this is really as

186
00:09:21.500 --> 00:09:24.400
 I mentioned the the number one platform

187
00:09:24.400 --> 00:09:27.000
 for web application security testing.

188
00:09:27.800 --> 00:09:30.000
But in case of fuzzing this is it

189
00:09:30.300 --> 00:09:33.900
 so there is a kind of a limitation but this

190
00:09:33.900 --> 00:09:36.400
 is a limitation related to the speed

191
00:09:36.400 --> 00:09:39.400
 of fuzzing the fuzzing still works very fine and

192
00:09:39.400 --> 00:09:42.500
 you will see it in a minute, but you cannot, you

193
00:09:42.500 --> 00:09:46.200
 know take out the most of it and because

194
00:09:45.200 --> 00:09:48.600
 this is this is the free edition, but in

195
00:09:48.600 --> 00:09:51.300
 terms of you know technical stuff it's

196
00:09:51.300 --> 00:09:54.200
 still works, but it will

197
00:09:54.200 --> 00:09:57.200
 be slow when you've got a long list of payloads. Okay.

198
00:09:57.200 --> 00:10:00.200
 So this is basically how it

199
00:10:00.200 --> 00:10:00.300
 works.

200
00:10:01.400 --> 00:10:04.200
So now my fuzzing is underway. You can see the

201
00:10:04.200 --> 00:10:07.800
 progress bar at the at the bottom of

202
00:10:07.800 --> 00:10:08.300
 my screen.

203
00:10:09.200 --> 00:10:12.200
So right now I need to wait, right? And this is how

204
00:10:12.200 --> 00:10:15.800
 it works. This attack is underway. And as I

205
00:10:15.800 --> 00:10:18.500
 mentioned this is the free edition, so it will slow

206
00:10:18.500 --> 00:10:22.100
 down when the time goes on but it

207
00:10:21.100 --> 00:10:24.300
 works perfectly good again. I really want

208
00:10:24.300 --> 00:10:27.200
 to emphasize this because I don't want to tell you

209
00:10:27.200 --> 00:10:30.200
 don't use at all free edition. No, you can still use

210
00:10:30.200 --> 00:10:33.500
 it but there are some limitations and I want to point them out,

211
00:10:33.500 --> 00:10:33.700
 right?

212
00:10:34.700 --> 00:10:37.500
Okay, the the fuzzing is underway. So I'm

213
00:10:37.500 --> 00:10:40.300
 going to post this video and I will come back in about

214
00:10:40.300 --> 00:10:43.400
 three four five minutes something like this when

215
00:10:43.400 --> 00:10:47.000
 the fuzzing is done. Then I'm gonna jump to

216
00:10:46.700 --> 00:10:49.800
 the interpretation of the results. Okay. So let

217
00:10:49.800 --> 00:10:52.600
 me post the video right now and let me get back

218
00:10:52.600 --> 00:10:53.800
 after a couple of minutes.

219
00:10:56.300 --> 00:10:57.500
Okay, guys, I'm back.

220
00:10:58.300 --> 00:11:01.500
After a couple of minutes, the fuzzing

221
00:11:01.500 --> 00:11:05.100
 is done right now. So the next

222
00:11:04.100 --> 00:11:08.000
 step is manual verification, right?

223
00:11:08.900 --> 00:11:11.300
So we asked burp Suite Intruder

224
00:11:11.300 --> 00:11:14.600
 to do an automated attack for us.

225
00:11:14.600 --> 00:11:17.600
 The automated attack has been

226
00:11:17.600 --> 00:11:20.600
 finished. Now. We need to go to manual

227
00:11:20.600 --> 00:11:23.600
 verification. We need to find out whether

228
00:11:23.600 --> 00:11:26.300
 there are some anomalies in

229
00:11:26.300 --> 00:11:29.200
 the responses or not. So this is exactly what I'm

230
00:11:29.200 --> 00:11:32.600
 going to do here. You see the different

231
00:11:32.600 --> 00:11:36.600
 responses, right? So like status code

232
00:11:35.600 --> 00:11:38.600
 length of response, right?

233
00:11:38.600 --> 00:11:41.500
 We can see different things like

234
00:11:41.500 --> 00:11:44.400
 weather error has occurred timeout stuff like

235
00:11:44.400 --> 00:11:47.000
 that and here of course, we've got payloads.

236
00:11:47.800 --> 00:11:50.100
And now we need to

237
00:11:50.100 --> 00:11:52.100
 find anomalies as I mentioned.

238
00:11:53.200 --> 00:11:56.700
So I'm going to do some kind of sorting right

239
00:11:56.700 --> 00:11:59.400
 now in ascending or descending order

240
00:11:59.400 --> 00:12:02.400
 just to see if we've got some anomalies or

241
00:12:02.400 --> 00:12:02.600
 not.

242
00:12:03.300 --> 00:12:05.400
So I will click status here.

243
00:12:06.300 --> 00:12:08.200
And sending descending orders, right?

244
00:12:08.900 --> 00:12:10.600
All the time, I see 200.

245
00:12:12.200 --> 00:12:15.300
Now error the same ascending descending.

246
00:12:17.100 --> 00:12:20.200
All the time. I see that you know,

247
00:12:20.200 --> 00:12:23.500
 nothing has changed timeout.

248
00:12:25.100 --> 00:12:28.500
The same no anomalies and length right

249
00:12:28.500 --> 00:12:28.600
 now.

250
00:12:30.800 --> 00:12:32.600
Oh, can you see something interesting?

251
00:12:34.200 --> 00:12:37.000
Now I've got a descending order.

252
00:12:38.100 --> 00:12:41.600
So for one payload the pale like this here.

253
00:12:43.200 --> 00:12:46.300
For this payload, I've got the length of

254
00:12:46.300 --> 00:12:50.600
 response 10,6004 and

255
00:12:49.600 --> 00:12:53.200
 for all other payloads the

256
00:12:52.200 --> 00:12:58.300
 length of response is 4,933. So

257
00:12:57.300 --> 00:13:00.500
 yeah, we've got an anomaly here,

258
00:13:00.500 --> 00:13:04.300
 right? And for some reason for this payload, we've

259
00:13:03.300 --> 00:13:07.100
 got a length of response like

260
00:13:06.100 --> 00:13:09.400
 over that 10,000 bytes,

261
00:13:09.400 --> 00:13:13.100
 right? It's interesting. So, let's see what we've

262
00:13:12.100 --> 00:13:15.600
 got here for the length for nine

263
00:13:15.600 --> 00:13:18.400
 free in the response. Let me analyze the

264
00:13:18.400 --> 00:13:19.200
 response right now.

265
00:13:21.500 --> 00:13:24.600
So in the response, I'll switch to

266
00:13:24.600 --> 00:13:26.000
 render here.

267
00:13:27.900 --> 00:13:30.600
Sorry, we can't find any seller

268
00:13:30.600 --> 00:13:32.400
 that matches search criteria, right?

269
00:13:33.400 --> 00:13:36.300
So this is what we see here when the length of

270
00:13:36.300 --> 00:13:40.000
 response is 4933 but here

271
00:13:39.500 --> 00:13:44.300
 when the length of response is 10,6004.

272
00:13:45.700 --> 00:13:48.700
I can see different names and

273
00:13:48.700 --> 00:13:51.300
 this is strange David Cooper Michael

274
00:13:51.300 --> 00:13:54.700
 green and Mark gross. These guys are the sellers and now

275
00:13:54.700 --> 00:13:57.900
 Russell Washington Angela Harris Daniel Robinson

276
00:13:57.900 --> 00:14:00.300
 Carl Martinez and a lot

277
00:14:00.300 --> 00:14:00.600
 more.

278
00:14:01.900 --> 00:14:03.800
Hmm this is surprising.

279
00:14:04.900 --> 00:14:07.100
So there are free sellers.

280
00:14:07.700 --> 00:14:10.600
in my online shopping platform,

281
00:14:10.600 --> 00:14:13.700
 and now when I provide this payload

282
00:14:14.600 --> 00:14:16.100
I see a lot more people.

283
00:14:17.500 --> 00:14:21.400
So most probably these people are customers because

284
00:14:20.400 --> 00:14:23.600
 if I've got free Sellers and I've

285
00:14:23.600 --> 00:14:26.900
 got online shopping platform and most probably the

286
00:14:26.900 --> 00:14:29.900
 rest guys are customers. So

287
00:14:29.900 --> 00:14:32.900
 it looks like we've got an SQL injection that

288
00:14:32.900 --> 00:14:35.400
 results in fetching more data

289
00:14:35.400 --> 00:14:38.900
 from the database than we are supposed to fetch. And

290
00:14:38.900 --> 00:14:41.700
 yeah, this is something that

291
00:14:41.700 --> 00:14:44.700
 really looks like a valid escuel injection and

292
00:14:44.700 --> 00:14:47.200
 you can take it right now and you

293
00:14:47.200 --> 00:14:50.300
 can report it to the backbounty program

294
00:14:50.300 --> 00:14:50.900
 owner.

295
00:14:51.600 --> 00:14:54.300
And you can get money for finding like

296
00:14:54.300 --> 00:14:57.600
 this one and this is how it works. So I found out

297
00:14:57.600 --> 00:15:01.600
 an anomaly and then I decided

298
00:15:00.600 --> 00:15:04.500
 you know to analyze what happened

299
00:15:03.500 --> 00:15:06.500
 here and I figured

300
00:15:06.500 --> 00:15:09.500
 out that most probably and I see also the

301
00:15:09.500 --> 00:15:12.100
 customers and I shouldn't be able to

302
00:15:12.100 --> 00:15:15.300
 see this data obviously. So yeah, it looks

303
00:15:15.300 --> 00:15:18.700
 like a true positive and here is the payload

304
00:15:18.700 --> 00:15:21.200
 that you have to

305
00:15:21.200 --> 00:15:25.500
 send out to the web application and then in response,

306
00:15:24.500 --> 00:15:27.100
 you're gonna see a lot more

307
00:15:27.100 --> 00:15:30.700
 data than you are actually supposed to see so this

308
00:15:30.700 --> 00:15:32.800
 is how it works. This is how fasting works.

309
00:15:33.600 --> 00:15:36.800
You see we've got an Automation and then manual verification

310
00:15:36.800 --> 00:15:39.700
 and now you can think about this payload

311
00:15:39.700 --> 00:15:42.800
 why this one payload results in

312
00:15:42.800 --> 00:15:45.500
 this kind of behavior? Why this

313
00:15:45.500 --> 00:15:48.700
 payload results in SQL injection and

314
00:15:48.700 --> 00:15:51.300
 I will give you an answer. You don't have

315
00:15:51.300 --> 00:15:55.100
 to go into the details here your point is

316
00:15:54.100 --> 00:15:57.900
 to to manual verification and

317
00:15:57.900 --> 00:16:00.700
 see if this is a true positive or false

318
00:16:00.700 --> 00:16:03.700
 positive. You really don't have to go into the details

319
00:16:03.700 --> 00:16:06.300
 of of you know, thinking of what might have

320
00:16:06.300 --> 00:16:09.800
 happened out there. This is also the power of fuzzing if

321
00:16:09.800 --> 00:16:12.400
 you know the recipe just apply this recipe

322
00:16:12.400 --> 00:16:15.800
 and then make an interpretation find

323
00:16:15.800 --> 00:16:18.300
 anomalies try to figure out

324
00:16:18.300 --> 00:16:21.100
 whether you've got a false positive or

325
00:16:21.100 --> 00:16:24.600
 too positive and you don't have to, you know, go into into

326
00:16:24.600 --> 00:16:27.400
 the details of a given payload because

327
00:16:27.400 --> 00:16:31.000
 you don't know the implementation again in 99% of

328
00:16:30.500 --> 00:16:33.300
 cases in backgrounds, you don't

329
00:16:33.500 --> 00:16:36.200
Know what is the implementation and you don't have to

330
00:16:36.200 --> 00:16:39.700
 know in Black Box testing. It works perfectly good.

331
00:16:39.700 --> 00:16:43.100
 I mean, you've got a payloads you analyze responses

332
00:16:42.100 --> 00:16:45.600
 you interpret the responses you interpret

333
00:16:45.600 --> 00:16:48.600
 the anomalies and you make some conclusions and and

334
00:16:48.600 --> 00:16:51.400
 based on this conclusions. You construct a report and

335
00:16:51.400 --> 00:16:54.600
 send it to the bug Bounty program owner. This is this is

336
00:16:54.600 --> 00:16:58.000
 how it works. So I want to tell you that you don't have to go into

337
00:16:57.300 --> 00:17:01.300
 the details of why this particular payload

338
00:17:00.300 --> 00:17:03.700
 my work or or maybe not working.

339
00:17:03.700 --> 00:17:07.300
 Right and this kind of stuff. I have found really

340
00:17:06.300 --> 00:17:09.400
 nice four digit bugs with

341
00:17:09.400 --> 00:17:12.200
 fuzzing where I had no idea why I given

342
00:17:12.200 --> 00:17:15.500
 payload work. I mean, I have some kind of ideas in

343
00:17:15.500 --> 00:17:18.300
 my mind but on the other hand, this is

344
00:17:18.300 --> 00:17:21.400
 Black Box testing and the goal here is to

345
00:17:21.400 --> 00:17:24.500
 prove that a given attack is possible. Right? And

346
00:17:24.500 --> 00:17:27.100
 that's it. That's what I want to tell you.

347
00:17:27.100 --> 00:17:30.200
 Okay. So basically this is it for

348
00:17:30.200 --> 00:17:33.400
 the first demo. I hope that you understand everything.

349
00:17:33.400 --> 00:17:36.300
Ink and if you don't understand everything don't worry

350
00:17:36.300 --> 00:17:41.300
 because in the next demo I'm going to do the

351
00:17:39.300 --> 00:17:42.400
 steps again, but in

352
00:17:42.400 --> 00:17:45.400
 the context of different different attack, so you

353
00:17:45.400 --> 00:17:48.100
 will have more opportunities to practice.

354
00:17:48.900 --> 00:17:51.800
With burp suit Intruder and fuzzing. So

355
00:17:51.800 --> 00:17:54.300
 I hope it has been informative for you and let me

356
00:17:54.300 --> 00:17:56.100
 now jump to the second demo.
