WEBVTT - This file was automatically generated by VIMEO

0
00:00:06.100 --> 00:00:10.500
Okay guys now it's time for case number one race

1
00:00:09.500 --> 00:00:12.400
 condition stealing money from

2
00:00:12.400 --> 00:00:15.000
 a bank. What I'm going

3
00:00:15.100 --> 00:00:18.300
 to present to you in this case is how to hack the

4
00:00:18.300 --> 00:00:21.200
 web application with multifreading.

5
00:00:22.200 --> 00:00:25.900
Multi-threading is very much related to

6
00:00:25.900 --> 00:00:26.900
 race conditions.

7
00:00:27.900 --> 00:00:31.200
In other words via multifredded attack,

8
00:00:30.200 --> 00:00:33.600
 we can trigger race condition

9
00:00:33.600 --> 00:00:36.800
 and Via race condition. We

10
00:00:36.800 --> 00:00:39.900
 can launch some really powerful attacks. For

11
00:00:39.900 --> 00:00:42.500
 example stealing money from a bank

12
00:00:42.500 --> 00:00:45.400
 and this is exactly what I'm going to show you

13
00:00:45.400 --> 00:00:46.500
 here in this case.

14
00:00:47.700 --> 00:00:50.300
Of course, I'm not going to

15
00:00:50.300 --> 00:00:53.700
 hack a real Bank. This is the training and

16
00:00:53.700 --> 00:00:56.600
 whatever. I'm presenting here is for educational

17
00:00:56.600 --> 00:00:59.200
 purposes only but to show you

18
00:00:59.200 --> 00:01:02.300
 how it works and to show you the power of race condition

19
00:01:02.300 --> 00:01:05.400
 exploitation. I need to have a demo and I have

20
00:01:05.400 --> 00:01:05.800
 one

21
00:01:06.700 --> 00:01:09.200
And my demo is located at training the

22
00:01:09.200 --> 00:01:13.000
 local/bank in my testing environment. So let

23
00:01:12.100 --> 00:01:15.100
 me go there right now and let me show

24
00:01:15.100 --> 00:01:17.500
 you how this attack Works step by step.

25
00:01:19.700 --> 00:01:22.800
Okay, here is my demo. What I

26
00:01:22.800 --> 00:01:25.700
 can do in this demo is I can transfer money

27
00:01:25.700 --> 00:01:28.400
 from one account to another account to

28
00:01:28.400 --> 00:01:31.200
 be more precise. I can transfer money from

29
00:01:31.200 --> 00:01:33.700
 Michael's account to James account.

30
00:01:34.500 --> 00:01:37.900
And the current balance is $1,000. So I

31
00:01:37.900 --> 00:01:40.600
 cannot transfer more than $1000

32
00:01:40.600 --> 00:01:43.300
 right? And if I try to do it

33
00:01:43.300 --> 00:01:48.600
 and for example, if I try to transfer 1,001

34
00:01:46.600 --> 00:01:49.100
 which is

35
00:01:49.100 --> 00:01:52.500
 more than 1,000 then I will

36
00:01:52.500 --> 00:01:56.400
 see a message failure. You don't have 1001 dollar.

37
00:01:56.400 --> 00:02:00.200
 Well, this is very much expected. And if

38
00:01:59.200 --> 00:02:02.100
 I was able to do it, then there would be

39
00:02:02.100 --> 00:02:03.400
 a disaster in the system, right?

40
00:02:04.500 --> 00:02:07.400
So this is how it works. This is how my

41
00:02:07.400 --> 00:02:11.100
 demo looks like. Okay, what

42
00:02:10.100 --> 00:02:13.200
 I'm going to do right now

43
00:02:13.200 --> 00:02:16.900
 is I'm going to move a smoothly

44
00:02:16.900 --> 00:02:19.300
 to the attack that

45
00:02:19.300 --> 00:02:22.500
 I'm going to actually present here and the attack is race conditions

46
00:02:22.500 --> 00:02:24.200
 the link money from a bank.

47
00:02:24.800 --> 00:02:27.600
So right now you can see that I cannot

48
00:02:27.600 --> 00:02:30.800
 transfer more money than I have. But what

49
00:02:30.800 --> 00:02:33.500
 you will see in the upcoming minutes of

50
00:02:33.500 --> 00:02:36.600
 this video is that actually I can

51
00:02:36.600 --> 00:02:40.400
 with row more money than I have via

52
00:02:39.400 --> 00:02:42.500
 race condition exploitation and it's

53
00:02:42.500 --> 00:02:45.800
 gonna be really great. You really beautiful and it's

54
00:02:45.800 --> 00:02:48.300
 gonna be an eye opener for for many

55
00:02:48.300 --> 00:02:51.300
 people that we can do something like this via race

56
00:02:51.300 --> 00:02:52.500
 condition exploitation.

57
00:02:53.300 --> 00:02:56.200
Okay. So yeah, let's do it. Let me

58
00:02:56.200 --> 00:02:57.400
 show you how it works.

59
00:02:58.300 --> 00:03:01.800
So now I'm gonna present to you how this

60
00:03:01.800 --> 00:03:04.400
 attack Works how to trigger race condition

61
00:03:04.400 --> 00:03:08.400
 and how to still money from a bank, but we

62
00:03:07.400 --> 00:03:10.700
 also need some technical explanation

63
00:03:10.700 --> 00:03:13.400
 behind this attack. So once this attack

64
00:03:13.400 --> 00:03:16.200
 is presented to you, once you see the power of

65
00:03:16.200 --> 00:03:19.800
 this attack, then I will jump to the Whiteboard and

66
00:03:19.800 --> 00:03:22.600
 I'll try to explain to you why it actually

67
00:03:22.600 --> 00:03:26.000
 works. Okay. So first I will present you that indeed

68
00:03:25.200 --> 00:03:28.400
 it works and how to make it work and

69
00:03:28.400 --> 00:03:31.900
 later on. I will explain you some technical details

70
00:03:31.900 --> 00:03:35.500
 behind this attack so that you can really understand in

71
00:03:34.500 --> 00:03:37.400
 you know, why it works

72
00:03:37.400 --> 00:03:40.200
 great. So let's do it. Let me

73
00:03:40.200 --> 00:03:42.900
 present this attack to you.

74
00:03:43.700 --> 00:03:47.000
As I told you at the very beginning we are

75
00:03:46.300 --> 00:03:50.300
 talking here about multifredded attack.

76
00:03:50.900 --> 00:03:53.500
So multi-threading is a

77
00:03:53.500 --> 00:03:57.000
 kind of prerequisite or starting point for

78
00:03:56.500 --> 00:03:57.700
 this attack.

79
00:03:58.500 --> 00:04:01.800
So we need a kind of a tool that supports

80
00:04:01.800 --> 00:04:02.800
 multi-threading.

81
00:04:03.400 --> 00:04:07.400
I could use burps with Pro which is

82
00:04:07.400 --> 00:04:11.600
 not a free tool you need to pay for this. But you

83
00:04:11.600 --> 00:04:15.300
 know, I just want you to be able to do all

84
00:04:14.300 --> 00:04:17.900
 the attacks that I'm presenting here with free

85
00:04:17.900 --> 00:04:20.400
 tools. So I'm going to

86
00:04:20.400 --> 00:04:23.400
 use over zap instead of

87
00:04:23.400 --> 00:04:26.500
 burps with Prof in my testing environment in

88
00:04:26.500 --> 00:04:27.700
 order to show you how it works.

89
00:04:28.600 --> 00:04:29.800
first let me

90
00:04:31.500 --> 00:04:32.700
open overs up.

91
00:04:38.400 --> 00:04:41.500
And what I have to do more right now the

92
00:04:41.500 --> 00:04:44.500
 ovas zap is up and running is I need

93
00:04:44.500 --> 00:04:47.400
 to tell my browser that now the

94
00:04:47.400 --> 00:04:50.700
 traffic send out from my browser should be actually sent

95
00:04:50.700 --> 00:04:53.800
 to overzab. Okay, so I

96
00:04:53.800 --> 00:04:55.200
 need to tell my browser about this.

97
00:04:56.500 --> 00:05:00.100
So yeah, now everything is let's say configured properly

98
00:04:59.100 --> 00:05:02.300
 over zap is up and

99
00:05:02.300 --> 00:05:05.400
 running and my browser knows that the traffic going out

100
00:05:05.400 --> 00:05:08.600
 from the browser should be sent to overzapp because

101
00:05:08.600 --> 00:05:11.800
 in a couple of minutes, I'm gonna use over zap

102
00:05:11.800 --> 00:05:14.300
 and multifreezing out there to launch

103
00:05:14.300 --> 00:05:17.600
 my attack. Okay. I hope that you are following me till this

104
00:05:17.600 --> 00:05:17.800
 point.

105
00:05:18.600 --> 00:05:21.500
Great. So now I'm about

106
00:05:21.500 --> 00:05:24.300
 to send and Money

107
00:05:24.300 --> 00:05:27.500
 Transfer request and what you can see here below is

108
00:05:27.500 --> 00:05:30.900
 amount $10. So yeah, let's send

109
00:05:30.400 --> 00:05:33.600
 $10 from one account to

110
00:05:33.600 --> 00:05:37.500
 another account and let's incorporate

111
00:05:36.500 --> 00:05:39.200
 this request related with

112
00:05:39.200 --> 00:05:43.200
 money transfer into multifredded

113
00:05:42.200 --> 00:05:44.300
 attack scenario. Okay.

114
00:05:45.100 --> 00:05:48.700
So this is exactly what I'm going to do right now. So first I

115
00:05:48.700 --> 00:05:51.600
 need to turn on the Interceptor in

116
00:05:51.600 --> 00:05:53.600
 the oversp.

117
00:05:55.100 --> 00:06:00.200
Now it is turned on and I'm going to click

118
00:05:58.200 --> 00:06:02.200
 send money. Okay? Let

119
00:06:01.200 --> 00:06:04.400
 me right now go to ovas zap.

120
00:06:05.500 --> 00:06:08.800
And what you can see is that indeed the request

121
00:06:08.800 --> 00:06:11.600
 has been intercepted and this request

122
00:06:11.600 --> 00:06:14.000
 is responsible for sending $10.

123
00:06:15.300 --> 00:06:19.200
From one account to another account, right and

124
00:06:18.200 --> 00:06:21.800
 I told you that the crucial part

125
00:06:21.800 --> 00:06:24.200
 here the starting point actually of

126
00:06:24.200 --> 00:06:28.300
 the attack is multi-threading. So I'm

127
00:06:27.300 --> 00:06:30.800
 going to take this request and

128
00:06:30.800 --> 00:06:33.800
 I'm going to incorporate this

129
00:06:33.800 --> 00:06:37.000
 request in multifred attack scenario.

130
00:06:36.600 --> 00:06:39.100
 And the question is how to

131
00:06:39.100 --> 00:06:42.300
 do it how to do it in oversupp. You can

132
00:06:42.300 --> 00:06:45.900
 do something like this. You can click right on this request. You

133
00:06:45.900 --> 00:06:47.000
 can click fuzz

134
00:06:48.700 --> 00:06:51.300
And well this request actually is

135
00:06:51.300 --> 00:06:54.400
 going to be used by the

136
00:06:54.400 --> 00:06:55.100
 father, right?

137
00:06:55.900 --> 00:06:58.200
And first we need to specify the

138
00:06:58.200 --> 00:07:01.800
 payload, you know position because this

139
00:07:01.800 --> 00:07:06.100
 is the father. So the father needs to know where the

140
00:07:05.100 --> 00:07:07.800
 fasting should happen in which place

141
00:07:09.200 --> 00:07:12.900
But in the context of this case that I have here, I

142
00:07:12.900 --> 00:07:16.200
 don't want to do a fuzzing over a specified parameter.

143
00:07:15.200 --> 00:07:18.700
 I just want to send this

144
00:07:18.700 --> 00:07:21.900
 request many times, you know concurrently in

145
00:07:21.900 --> 00:07:24.800
 the multifred manner. So the payloads gonna

146
00:07:24.800 --> 00:07:27.600
 be now empty right, but I have to tell this

147
00:07:27.600 --> 00:07:30.600
 message, you know to to the

148
00:07:30.600 --> 00:07:33.100
 father so that it knows that the payload is

149
00:07:33.100 --> 00:07:36.200
 now empty. So I'm gonna go to payloads right

150
00:07:36.200 --> 00:07:38.200
 now. I'm gonna click add.

151
00:07:40.100 --> 00:07:43.300
And I'm gonna choose empty now.

152
00:07:44.100 --> 00:07:47.400
And now number of repetitions. So how many

153
00:07:47.400 --> 00:07:51.100
 times I want to ascend this,

154
00:07:50.100 --> 00:07:53.800
 you know request actually

155
00:07:53.800 --> 00:07:56.600
 to do web application, let it

156
00:07:56.600 --> 00:07:59.700
 be like 200. Okay. Why

157
00:07:59.700 --> 00:07:59.900
 not?

158
00:08:01.100 --> 00:08:04.900
So yeah, this is it and I'm gonna click ok, so I

159
00:08:04.900 --> 00:08:07.800
 am about to send this one particular

160
00:08:07.800 --> 00:08:10.100
 request 200 times.

161
00:08:11.200 --> 00:08:15.700
To do web application and this request is about money transfer

162
00:08:15.200 --> 00:08:18.600
 $10 from one account to another so in

163
00:08:18.600 --> 00:08:21.600
 the best case scenario from

164
00:08:21.600 --> 00:08:24.400
 the attacker's point of view. I will

165
00:08:24.400 --> 00:08:28.000
 be able to withdraw 200 times

166
00:08:27.800 --> 00:08:30.300
 10 dollars right from the

167
00:08:30.300 --> 00:08:34.300
 account. So $2,000. This is the hypothetical

168
00:08:33.300 --> 00:08:36.500
 theoretical the best

169
00:08:36.500 --> 00:08:39.200
 case scenario, right? So if I'm able to

170
00:08:39.200 --> 00:08:42.700
 if I am actually making a money transfer ten

171
00:08:42.700 --> 00:08:45.600
 dollars 200 times then if this exploit

172
00:08:45.600 --> 00:08:47.500
 works then at maximum I can

173
00:08:48.500 --> 00:08:51.200
You know, we've wrote $2,000 but this

174
00:08:51.200 --> 00:08:54.200
 is a theoretical maximum. You will see what it means

175
00:08:54.200 --> 00:08:57.400
 actually later on in this video. Okay, so I

176
00:08:57.400 --> 00:09:00.500
 believe that this is clear for you. So so far we have

177
00:09:00.500 --> 00:09:03.500
 configured the father to send one

178
00:09:03.500 --> 00:09:06.500
 request 200 times without any

179
00:09:06.500 --> 00:09:10.200
 modifications just the same request. But as

180
00:09:09.200 --> 00:09:12.200
 I told you a couple of times

181
00:09:12.200 --> 00:09:15.700
 already in this video multifreading is the prerequisite

182
00:09:15.700 --> 00:09:18.200
 for this attack. So now you need to

183
00:09:18.200 --> 00:09:19.600
 go to options here.

184
00:09:20.600 --> 00:09:24.900
And there is something like concurrent scanning

185
00:09:24.900 --> 00:09:27.700
 threads per scan here. Our

186
00:09:27.700 --> 00:09:30.700
 multi-threading can be configured.

187
00:09:30.700 --> 00:09:33.700
 So let's choose. For example 20

188
00:09:33.700 --> 00:09:36.800
 right now. The concurrent scanning

189
00:09:36.800 --> 00:09:39.400
 Frets per scan is 20. This is

190
00:09:39.400 --> 00:09:43.500
 how I'm configuring multifredded attack

191
00:09:43.500 --> 00:09:47.200
 in my father. Okay, which is really fundamental piece

192
00:09:46.200 --> 00:09:49.100
 of of this exploit here.

193
00:09:50.300 --> 00:09:50.700
Great.

194
00:09:51.600 --> 00:09:54.700
So right now I've got everything I've

195
00:09:54.700 --> 00:09:57.700
 got multifredding implemented. I'm about

196
00:09:57.700 --> 00:10:00.400
 to send this request 200 times. So

197
00:10:00.400 --> 00:10:03.400
 let me do it right now and let me click Start further.

198
00:10:04.700 --> 00:10:06.200
You know, it's blazing fast.

199
00:10:07.400 --> 00:10:10.000
We've got multifreading we've got concurrency here.

200
00:10:11.100 --> 00:10:14.500
So it has been finished very quickly.

201
00:10:14.500 --> 00:10:18.000
 Now, let me release the Interceptor here.

202
00:10:17.100 --> 00:10:20.100
 Let me refresh my

203
00:10:20.100 --> 00:10:23.500
 web application and let me show you what's the consequence of

204
00:10:23.500 --> 00:10:25.200
 of this attack? Okay.

205
00:10:26.800 --> 00:10:29.800
What you can see here is that.

206
00:10:30.600 --> 00:10:36.900
Well, I was able to transfer 1,090. It's

207
00:10:35.900 --> 00:10:38.400
 really cool. I had

208
00:10:38.400 --> 00:10:42.100
 only 1,000 and I was able to transfer

209
00:10:41.100 --> 00:10:45.900
 more I was able to transfer 1090

210
00:10:44.900 --> 00:10:47.800
 so you can clearly see Michael

211
00:10:47.800 --> 00:10:52.800
 zillord dollars James 1090. It's

212
00:10:52.800 --> 00:10:55.700
 just you know amazing. It works. This

213
00:10:55.700 --> 00:10:59.300
 is how you can actually use multifreading to

214
00:10:59.300 --> 00:11:02.400
 trigger race condition and Via race condition how

215
00:11:02.400 --> 00:11:05.100
 we can still some money from a bank. So what I have

216
00:11:05.100 --> 00:11:08.700
 presented so far to you is how this

217
00:11:08.700 --> 00:11:11.700
 attack works and how to make it work. Okay,

218
00:11:11.700 --> 00:11:15.100
 and you see the power of this attack, but what

219
00:11:14.100 --> 00:11:17.300
 I have to do more in this

220
00:11:17.300 --> 00:11:20.200
 video is I just want to explain to you

221
00:11:20.200 --> 00:11:22.200
 why it works. Okay.

222
00:11:23.400 --> 00:11:26.700
So let me go right now to the Whiteboard and

223
00:11:26.700 --> 00:11:30.000
 let me provide some more explanation.
