WEBVTT - This file was automatically generated by VIMEO

0
00:00:06.300 --> 00:00:09.300
Okay, guys, welcome back in the second

1
00:00:09.300 --> 00:00:09.800
 demo.

2
00:00:10.400 --> 00:00:13.400
In this demo, I'm going to show you

3
00:00:13.400 --> 00:00:16.200
 how to use burp suit Intruder to

4
00:00:16.200 --> 00:00:19.700
 do fuzzing for path traversal. I've

5
00:00:19.700 --> 00:00:22.500
 got here the same testing web

6
00:00:22.500 --> 00:00:26.000
 application. So this is an online shopping platform. And

7
00:00:25.400 --> 00:00:28.600
 now I'm gonna change the language the

8
00:00:28.600 --> 00:00:31.300
 preferred language. The default one is English now, I'm

9
00:00:31.300 --> 00:00:32.500
 Gonna Change it to German.

10
00:00:33.900 --> 00:00:36.600
And you see the message this language is not supported

11
00:00:36.600 --> 00:00:39.800
 yet. Okay, what's more

12
00:00:39.800 --> 00:00:42.900
 the value of this language is sent

13
00:00:42.900 --> 00:00:46.200
 in the URL. I believe that you can see it. There is

14
00:00:45.200 --> 00:00:48.400
 a parameter named language with

15
00:00:48.400 --> 00:00:51.400
 the value German. So let me now change the

16
00:00:51.400 --> 00:00:52.600
 value to English.

17
00:00:56.500 --> 00:00:59.300
And you see the message your language has

18
00:00:59.300 --> 00:01:00.300
 been changed to English.

19
00:01:01.200 --> 00:01:01.700
call

20
00:01:02.700 --> 00:01:05.700
and now I'm going to provide some arbitrary data.

21
00:01:08.300 --> 00:01:11.900
This language is not supported yet. Well for sure

22
00:01:11.900 --> 00:01:13.000
 it is not supported yet.

23
00:01:14.100 --> 00:01:17.900
And now let me think about it. What is happening

24
00:01:17.900 --> 00:01:20.400
 here or what might be happening here.

25
00:01:21.200 --> 00:01:24.700
When we've got different translations, you know

26
00:01:24.700 --> 00:01:27.800
 different translations of web pages,

27
00:01:27.800 --> 00:01:30.700
 then it may happen that this

28
00:01:30.700 --> 00:01:33.600
 translations are fetched from a file.

29
00:01:34.300 --> 00:01:37.700
From the web server, right? So let's

30
00:01:37.700 --> 00:01:38.900
 assume that we've got for example.

31
00:01:39.900 --> 00:01:42.600
Language like English and Chinese,

32
00:01:42.600 --> 00:01:43.100
 okay.

33
00:01:43.900 --> 00:01:47.100
And we can have two

34
00:01:46.100 --> 00:01:49.200
 different files with two

35
00:01:49.200 --> 00:01:52.900
 different translations. And when we change this language

36
00:01:52.900 --> 00:01:55.300
 preferred language from English to Chinese

37
00:01:55.300 --> 00:01:58.100
 to Japanese, whatever and then it may happen

38
00:01:58.100 --> 00:02:01.500
 that this translations are taken out from the

39
00:02:01.500 --> 00:02:04.600
 files on the web server and

40
00:02:04.600 --> 00:02:07.700
 then they are just, you know returned to

41
00:02:07.700 --> 00:02:10.200
 us to users. This is how

42
00:02:10.200 --> 00:02:13.300
 it works in in different web

43
00:02:13.300 --> 00:02:13.800
 applications.

44
00:02:14.700 --> 00:02:17.500
And when something like this happens,

45
00:02:17.500 --> 00:02:21.800
 then it may be possible via language

46
00:02:21.800 --> 00:02:24.000
 parameter to fetch other

47
00:02:24.900 --> 00:02:27.600
 a files from the file system of

48
00:02:27.600 --> 00:02:30.300
 the web server, right? It may be possible. You

49
00:02:30.300 --> 00:02:33.400
 never know. You never know how it works on the server

50
00:02:33.400 --> 00:02:36.100
 side. You can just you know use your own

51
00:02:36.100 --> 00:02:39.100
 experience. You can just you know have to

52
00:02:39.100 --> 00:02:43.000
 make some interpretation here about the context and

53
00:02:42.400 --> 00:02:45.300
 now I'm not saying that for

54
00:02:45.300 --> 00:02:48.600
 sure it works this way. I as a backhander

55
00:02:48.600 --> 00:02:51.400
 need to you know, imagine what may

56
00:02:51.400 --> 00:02:54.400
 happen and when I see something like this that

57
00:02:54.400 --> 00:02:57.700
 it may happen that the translations are fetched

58
00:02:57.700 --> 00:03:00.900
 from the files from the file system

59
00:03:00.900 --> 00:03:03.300
 of web server. Then what comes

60
00:03:03.300 --> 00:03:06.300
 up to my mind is potentially I may be

61
00:03:06.300 --> 00:03:07.900
 able to do puff traversal attack.

62
00:03:08.600 --> 00:03:11.400
What I can do as a result of puff traversal attack

63
00:03:11.400 --> 00:03:15.900
 is I can fetch arbitrary files

64
00:03:15.900 --> 00:03:18.500
 from the file system of the web server,

65
00:03:18.500 --> 00:03:21.700
 right? So you see this this kind of thinking and

66
00:03:21.700 --> 00:03:24.200
 and this kind of thinking is very important at the very

67
00:03:24.200 --> 00:03:24.700
 beginning. Okay?

68
00:03:25.800 --> 00:03:28.700
Okay, so far so good. So let's

69
00:03:28.700 --> 00:03:31.800
 do fuzzing of language parameter for

70
00:03:31.800 --> 00:03:35.100
 path traversal. It makes sense because

71
00:03:34.100 --> 00:03:37.400
 I man might be

72
00:03:37.400 --> 00:03:40.400
 successful. When I do this kind of testing and I try

73
00:03:40.400 --> 00:03:44.200
 to explain you why I think in this way, okay. So

74
00:03:43.200 --> 00:03:47.600
 now I'm gonna resend this

75
00:03:46.600 --> 00:03:50.600
 request and I'm gonna intercept this

76
00:03:50.600 --> 00:03:53.700
 request in proxy. So I'm gonna repeat the

77
00:03:53.700 --> 00:03:56.500
 steps from the previous from the previous demo. So

78
00:03:56.500 --> 00:03:59.700
 let me turn on the Interceptor now, let's go

79
00:03:59.700 --> 00:04:02.300
 here to do a application. I'm gonna

80
00:04:02.300 --> 00:04:03.000
 hit enter.

81
00:04:04.100 --> 00:04:05.800
let's go back to

82
00:04:07.300 --> 00:04:10.800
The proxy here it is the intercepted request.

83
00:04:10.800 --> 00:04:14.400
 You see we've got language parameter with

84
00:04:13.400 --> 00:04:16.500
 arbitrary, you know

85
00:04:16.500 --> 00:04:19.800
 value but the value does not matter. It's gonna be in a

86
00:04:19.800 --> 00:04:22.500
 minute placeholder for my malicious payloads,

87
00:04:22.500 --> 00:04:25.600
 but later on now click right

88
00:04:25.600 --> 00:04:27.700
 send it to intruder.

89
00:04:28.600 --> 00:04:30.700
Now, let's go to intruder.

90
00:04:32.600 --> 00:04:34.700
Let's go to positions.

91
00:04:35.500 --> 00:04:37.500
Everything is highlighted right now.

92
00:04:38.400 --> 00:04:39.900
So let me clear it out.

93
00:04:40.700 --> 00:04:43.900
Now I want the value of language parameter

94
00:04:43.900 --> 00:04:46.700
 to be a placeholder. So let me highlight it.

95
00:04:47.800 --> 00:04:50.600
And once it is highlighted, I need to click

96
00:04:50.600 --> 00:04:51.100
 add.

97
00:04:52.300 --> 00:04:55.100
And now this is a placeholder for my

98
00:04:55.100 --> 00:04:58.800
 malicious payloads. The attack type is sniper. You

99
00:04:58.800 --> 00:05:00.100
 already know what it is.

100
00:05:01.300 --> 00:05:03.900
And now let me go to the payloads.

101
00:05:05.300 --> 00:05:09.300
payload options simple list load and

102
00:05:08.300 --> 00:05:11.500
 this time well again,

103
00:05:11.500 --> 00:05:14.400
 I'm interested in this list of

104
00:05:14.400 --> 00:05:17.800
 payloads from from

105
00:05:17.800 --> 00:05:21.000
 this location and but this

106
00:05:20.000 --> 00:05:21.400
 time

107
00:05:22.400 --> 00:05:25.500
I am interested in traversal.txt right

108
00:05:25.500 --> 00:05:28.400
 because I'm gonna do fuzzing for

109
00:05:28.400 --> 00:05:29.400
 past traversal.

110
00:05:30.500 --> 00:05:33.500
And let me click open right

111
00:05:33.500 --> 00:05:33.800
 now.

112
00:05:35.200 --> 00:05:38.100
And I've got a bunch of different payloads for pathfroversal.

113
00:05:38.700 --> 00:05:41.500
And now when you've got a burp suit

114
00:05:41.500 --> 00:05:45.000
 professional Edition, then you can add your

115
00:05:44.300 --> 00:05:47.700
 payloads from this list right from

116
00:05:47.700 --> 00:05:50.800
 the list of burp suit pro at payloads,

117
00:05:50.800 --> 00:05:53.500
 but in free edition of perp Suite

118
00:05:53.500 --> 00:05:55.200
 you don't have this list.

119
00:05:56.300 --> 00:05:59.500
And this is the additional reason why I'm

120
00:05:59.500 --> 00:06:03.200
 presenting the list of payloads from wfas because

121
00:06:02.200 --> 00:06:05.300
 you can take them for free and you

122
00:06:05.300 --> 00:06:08.300
 can launch your fuzzing and you will really be

123
00:06:08.300 --> 00:06:11.300
 successfully many cases. So again, you don't have

124
00:06:11.300 --> 00:06:14.500
 to have burp suit Pro. It's helpful

125
00:06:14.500 --> 00:06:17.100
 when you've got burps with Pro because there are no

126
00:06:17.100 --> 00:06:20.500
 limitations related the speed of fuzzing and you've got

127
00:06:20.500 --> 00:06:23.400
 in burp suit Pro the list of payloads for

128
00:06:23.400 --> 00:06:26.300
 different attacks, but it is not necessary. Right?

129
00:06:26.300 --> 00:06:29.800
 And this is what I'm trying to explain to you. Okay, so

130
00:06:29.800 --> 00:06:30.900
 we've got everything right now.

131
00:06:32.100 --> 00:06:36.600
So we need to start our attack. So let's go to Intruder. Click

132
00:06:35.600 --> 00:06:38.300
 Start attack again. We see

133
00:06:38.300 --> 00:06:41.800
 this message about a time throttle

134
00:06:41.800 --> 00:06:44.700
 attacks. This is what I already explained to you. Let

135
00:06:44.700 --> 00:06:47.400
 me click. Okay, and yeah, then

136
00:06:47.400 --> 00:06:50.700
 the fuzzing is underway.

137
00:06:50.700 --> 00:06:53.900
 So again, we have to wait and a

138
00:06:53.900 --> 00:06:54.400
 couple of minutes.

139
00:06:55.500 --> 00:06:58.700
Or sometimes well, it depends actually on

140
00:06:58.700 --> 00:07:01.200
 your list of payloads. If

141
00:07:01.200 --> 00:07:04.800
 you've got a very long list of payloads, then it

142
00:07:04.800 --> 00:07:08.000
 will be longer. Right but approximately

143
00:07:07.200 --> 00:07:10.500
 you have to wait a

144
00:07:10.500 --> 00:07:13.400
 couple of minutes and until it is finished.

145
00:07:13.400 --> 00:07:16.200
 So let me right now post the video and

146
00:07:16.200 --> 00:07:18.400
 let me get back to you once it is done.

147
00:07:21.300 --> 00:07:24.600
Okay, the fuzzing has finished.

148
00:07:24.600 --> 00:07:27.400
 So now the next part is

149
00:07:27.400 --> 00:07:30.200
 manual verification. So as you already know we

150
00:07:30.200 --> 00:07:34.100
 need to find out whether there are some anomalies

151
00:07:33.100 --> 00:07:36.800
 out there. So let me first, you

152
00:07:36.800 --> 00:07:39.000
 know, make it a little bit bigger because you don't see the

153
00:07:39.400 --> 00:07:42.100
 payloads out there. So yeah anomalies let

154
00:07:42.100 --> 00:07:45.600
 me do again some sorting ascending the sending order for

155
00:07:45.600 --> 00:07:48.700
 different, you know for different

156
00:07:48.700 --> 00:07:49.900
 things like status.

157
00:07:50.900 --> 00:07:54.000
I don't see an anomalies for error. Also.

158
00:07:53.200 --> 00:07:57.000
 I don't see for timeout no length.

159
00:07:59.200 --> 00:08:02.000
Oh, there is something interesting. Can you see

160
00:08:02.500 --> 00:08:04.300
 now? I've got a descending order.

161
00:08:05.600 --> 00:08:08.700
And I've got many different lengths.

162
00:08:09.700 --> 00:08:12.500
3731

163
00:08:14.600 --> 00:08:15.000
right

164
00:08:16.200 --> 00:08:19.200
And I've got a couple I got

165
00:08:19.200 --> 00:08:21.800
 three lengths 6000.

166
00:08:22.600 --> 00:08:25.900
297 it's interesting. Let's

167
00:08:25.900 --> 00:08:28.300
 see. What what's that when I've got for

168
00:08:28.300 --> 00:08:31.000
 example this one 3731

169
00:08:31.700 --> 00:08:33.900
What's the what's the response?

170
00:08:36.400 --> 00:08:39.500
The response is this language is not supported yet.

171
00:08:39.500 --> 00:08:43.400
 Okay, so I provided a lot of payloads that

172
00:08:42.400 --> 00:08:46.200
 resulted in this response. This

173
00:08:46.200 --> 00:08:49.500
 language is not supported yet. It makes sense. But what happened

174
00:08:49.500 --> 00:08:51.600
 for this payloads here?

175
00:08:53.200 --> 00:08:56.300
Oh, what a nice response. Can you

176
00:08:56.300 --> 00:08:56.700
 see that?

177
00:08:57.600 --> 00:09:00.500
This is this is the content of

178
00:09:00.200 --> 00:09:02.500
 Etc past WD.

179
00:09:03.200 --> 00:09:06.900
So this is a nice proof of concept showing that

180
00:09:06.900 --> 00:09:09.100
 path traversal indeed is

181
00:09:09.100 --> 00:09:12.200
 possible. I was able to fetch the file.

182
00:09:12.200 --> 00:09:16.100
 That should not be visible to me. Right? And yeah

183
00:09:15.100 --> 00:09:18.700
 puff traversal is possible and

184
00:09:18.700 --> 00:09:21.300
 you can see that this is

185
00:09:21.300 --> 00:09:24.700
 a very nice proof of concept for puff traversal. I

186
00:09:24.700 --> 00:09:27.500
 can use puff traversal tag

187
00:09:27.500 --> 00:09:30.400
 via language parameter and

188
00:09:30.400 --> 00:09:34.200
 I can extract arbitral files

189
00:09:33.200 --> 00:09:36.100
 from the file system of the

190
00:09:36.100 --> 00:09:40.300
 web server. Very nice. Very cool. And this

191
00:09:39.300 --> 00:09:42.900
 is it just take this payload. You

192
00:09:42.900 --> 00:09:46.000
 can see this payload here that was responsible for

193
00:09:45.400 --> 00:09:48.100
 fetching the content of this

194
00:09:48.100 --> 00:09:52.000
 file the Slash the slash those slash a

195
00:09:51.100 --> 00:09:54.400
 couple of times Etc past WD

196
00:09:54.400 --> 00:09:57.700
 and percent zero zero, which is URL included

197
00:09:57.700 --> 00:10:01.700
 now character and when we've got this payload,

198
00:10:00.700 --> 00:10:02.600
 then we can see

199
00:10:03.100 --> 00:10:06.300
Add the content of EDC +

200
00:10:06.300 --> 00:10:08.500
 WD file, which is really cool.

201
00:10:09.800 --> 00:10:13.600
So now you can see yet another example of how

202
00:10:12.600 --> 00:10:15.500
 to use burp suit

203
00:10:15.500 --> 00:10:18.600
 Intruder for fuzzing and it was presented in

204
00:10:18.600 --> 00:10:21.900
 the context of tough traversal, but

205
00:10:21.900 --> 00:10:24.300
 this knowledge is is you

206
00:10:24.300 --> 00:10:28.000
 know, generic what I mean here is that you've got

207
00:10:27.200 --> 00:10:30.700
 and recipe right. Now, you can

208
00:10:30.700 --> 00:10:33.800
 apply this recipe to find a

209
00:10:33.800 --> 00:10:36.700
 different vulnerabilities in

210
00:10:36.700 --> 00:10:39.300
 web applications. Right? So we've got a recipe for

211
00:10:39.300 --> 00:10:42.000
 fuzzing with burp suit Intruder now, you just need to

212
00:10:42.400 --> 00:10:46.500
 take a list of payloads dependently on

213
00:10:45.500 --> 00:10:48.500
 what you are looking

214
00:10:48.500 --> 00:10:51.500
 for right dependently on the context in the

215
00:10:51.500 --> 00:10:55.800
 previous demo. I presented to you how to do fuzzing

216
00:10:55.800 --> 00:10:58.800
 for SQL injection in this demo how to do fuzzing for

217
00:10:58.800 --> 00:11:01.300
 pastoral but there are other lists as well

218
00:11:01.300 --> 00:11:04.500
 for XML for xss for bad

219
00:11:04.500 --> 00:11:07.400
 characters, right? I present to you the list

220
00:11:07.400 --> 00:11:09.500
 of payloads in wfus.

221
00:11:09.700 --> 00:11:12.400
Different classes of vulnerabilities right but when

222
00:11:12.400 --> 00:11:15.600
 you've got this recipe, then you can just you've got

223
00:11:15.600 --> 00:11:18.100
 the doors open right now. You can do

224
00:11:18.100 --> 00:11:21.400
 a lot of testing on your own because you've got the recipe

225
00:11:21.400 --> 00:11:24.900
 this is this is the most important thing and

226
00:11:24.900 --> 00:11:28.100
 yeah, this is what I wanted to tell you at the

227
00:11:28.100 --> 00:11:31.300
 very end of this demo. So I hope that it is right

228
00:11:31.300 --> 00:11:34.200
 now clear for you and let me right now

229
00:11:34.200 --> 00:11:35.700
 jump to another video.
