WEBVTT - This file was automatically generated by VIMEO

0
00:00:13.400 --> 00:00:15.800
Hello everyone and welcome to this lesson.

1
00:00:16.400 --> 00:00:19.500
In this lesson, we are going to understand that with

2
00:00:19.500 --> 00:00:23.000
 the help of nuclei. We can also perform fuzzing.

3
00:00:22.600 --> 00:00:25.700
 This can be super useful for us if

4
00:00:25.700 --> 00:00:29.000
 we are trying to fuzz the parameters

5
00:00:28.300 --> 00:00:31.300
 for some default usernames and

6
00:00:31.300 --> 00:00:32.000
 default passwords.

7
00:00:33.100 --> 00:00:37.200
This helps us identify Security misconfigurations on

8
00:00:36.200 --> 00:00:39.700
 multiple targets sub domains

9
00:00:39.100 --> 00:00:42.500
 Etc if they are running all default username

10
00:00:42.500 --> 00:00:43.000
 or password.

11
00:00:44.400 --> 00:00:47.900
We can also use this to First for URL endpoints

12
00:00:47.900 --> 00:00:48.100
 as well.

13
00:00:49.300 --> 00:00:53.600
In this specific lesson. We are going to understand how you

14
00:00:52.600 --> 00:00:55.300
 can run various types

15
00:00:55.300 --> 00:00:57.300
 of payload using nuclei.

16
00:00:58.800 --> 00:01:01.400
We will be using the payload from a word

17
00:01:01.400 --> 00:01:04.400
 list file or we can also use a normal list file.

18
00:01:05.900 --> 00:01:08.200
Payloads can be defined in the

19
00:01:08.200 --> 00:01:11.100
 nuclei template with the help of payloads colon.

20
00:01:12.800 --> 00:01:15.100
So the first fuzzing technique that we are

21
00:01:15.100 --> 00:01:17.200
 going to see is cluster pump.

22
00:01:17.800 --> 00:01:19.900
So what exactly is cluster bomb?

23
00:01:21.200 --> 00:01:24.100
Let's assume we have assigned in page which has a

24
00:01:24.100 --> 00:01:26.600
 username field and a password field.

25
00:01:28.100 --> 00:01:32.500
In cluster bomb Technique, we are going to take one value.

26
00:01:33.600 --> 00:01:37.000
From the word list and Supply it in the username one

27
00:01:36.500 --> 00:01:39.400
 value from the password and Supply into

28
00:01:39.400 --> 00:01:40.000
 the password.

29
00:01:41.100 --> 00:01:44.000
Similarly for the next attempt. We are going to

30
00:01:44.300 --> 00:01:47.700
 take again the first value itself and the

31
00:01:47.700 --> 00:01:50.000
 second password from the word list.

32
00:01:50.700 --> 00:01:53.400
Similarly first username third password

33
00:01:53.400 --> 00:01:56.500
 first username fourth password and so

34
00:01:56.500 --> 00:01:56.500
 on.

35
00:01:57.500 --> 00:02:01.100
So we are using different combinations to First

36
00:02:00.100 --> 00:02:03.900
 the application to identify if

37
00:02:03.900 --> 00:02:06.600
 we are successfully able to authenticate into

38
00:02:06.600 --> 00:02:09.400
 a application with the help of cluster bomb

39
00:02:09.400 --> 00:02:10.000
 technique.

40
00:02:11.900 --> 00:02:14.500
In simple terms, we fix the payload

41
00:02:14.500 --> 00:02:17.500
 one and we iterate for payload 2 and we

42
00:02:17.500 --> 00:02:20.100
 do that continuously for payload 2

43
00:02:20.100 --> 00:02:22.200
 3 4 5 Etc.

44
00:02:23.600 --> 00:02:26.900
So it is the Practical time and let's understand how exactly

45
00:02:26.900 --> 00:02:29.300
 we can use the cluster bomb

46
00:02:29.300 --> 00:02:31.900
 fuzzing technique with the help of nuclei.

47
00:02:32.800 --> 00:02:35.700
So you can see over here. This is the Target that

48
00:02:35.700 --> 00:02:37.000
 we are going to use for testing.

49
00:02:38.200 --> 00:02:41.700
I want to endpoint which is nuclei slash fuzzing test

50
00:02:41.700 --> 00:02:42.900
 dot PHP.

51
00:02:44.100 --> 00:02:47.700
Here you can see I have supplied a username as admin. I'm

52
00:02:47.700 --> 00:02:50.900
 going to supply a password as test and

53
00:02:50.900 --> 00:02:51.800
 hit on login.

54
00:02:53.100 --> 00:02:56.300
When I do that if you look very carefully in the request.

55
00:02:57.300 --> 00:03:00.200
The username parameter contains the username that

56
00:03:00.200 --> 00:03:03.500
 was supplied the password parameter contains the password

57
00:03:03.500 --> 00:03:06.800
 that I just supplied and there is a login button

58
00:03:06.800 --> 00:03:09.100
 which is equals to login.

59
00:03:10.500 --> 00:03:14.100
You will be able to see the same thing when we capture

60
00:03:13.100 --> 00:03:16.200
 this request in burpsute as well.

61
00:03:17.400 --> 00:03:20.500
You can see as the password was incorrect. We got a

62
00:03:20.500 --> 00:03:22.100
 field login attempt.

63
00:03:23.100 --> 00:03:26.600
Let us change this to Batman and hit enter.

64
00:03:27.900 --> 00:03:30.300
And you can see this was again a field

65
00:03:30.300 --> 00:03:31.600
 login attempt.

66
00:03:32.500 --> 00:03:35.800
Let's try the default password as admin itself

67
00:03:35.800 --> 00:03:36.900
 and hit enter.

68
00:03:38.100 --> 00:03:41.700
And you can see the password admin was correct,

69
00:03:41.700 --> 00:03:44.600
 and we got a message which is success.

70
00:03:45.900 --> 00:03:46.300
Great.

71
00:03:47.400 --> 00:03:51.100
Now we are going to write a custom template that

72
00:03:50.100 --> 00:03:53.000
 we can use for fuzzing.

73
00:03:54.400 --> 00:03:57.700
So as you can see over here, I have written first in

74
00:03:57.700 --> 00:04:00.600
 cluster Bomb Dot. Yml template. Let's quickly understand.

75
00:04:00.600 --> 00:04:03.500
 How does this template look like and

76
00:04:03.500 --> 00:04:05.800
 how you can also write your own templates.

77
00:04:07.500 --> 00:04:10.300
The first is the ID block which contains the name of

78
00:04:10.300 --> 00:04:10.900
 the template.

79
00:04:11.600 --> 00:04:15.200
Next is the info block which contains basic information

80
00:04:15.200 --> 00:04:16.300
 about the template.

81
00:04:17.800 --> 00:04:19.500
Next is the request block.

82
00:04:20.600 --> 00:04:23.600
I'm using a raw HTTP request right

83
00:04:23.600 --> 00:04:23.700
 now.

84
00:04:24.500 --> 00:04:27.500
You can see the HTTP method is get.

85
00:04:28.300 --> 00:04:31.400
I'm sending a request to this specific endpoint and we

86
00:04:31.400 --> 00:04:34.300
 have seen the same thing in our browser as

87
00:04:34.300 --> 00:04:34.500
 well.

88
00:04:35.500 --> 00:04:38.800
Username equals to we don't know the username. So

89
00:04:38.800 --> 00:04:41.400
 we are going to specify that as parameter a

90
00:04:41.400 --> 00:04:44.100
 we don't know the password. So we are going

91
00:04:44.100 --> 00:04:47.700
 to specify the password field or the password parameter as

92
00:04:47.700 --> 00:04:50.500
 parameter B and login equals to

93
00:04:50.500 --> 00:04:53.200
 login. Let's see the same thing over

94
00:04:53.200 --> 00:04:54.400
 here once again.

95
00:04:55.200 --> 00:04:58.900
Username equals to parameter a password equals

96
00:04:58.900 --> 00:05:01.600
 to parameter B and login equals to

97
00:05:01.600 --> 00:05:02.200
 login.

98
00:05:03.200 --> 00:05:06.500
Let's go back over here. This is the same request

99
00:05:06.500 --> 00:05:09.900
 as it is. Let's go and check the payloads.

100
00:05:10.800 --> 00:05:13.700
In the payload block you can see we have specified

101
00:05:13.700 --> 00:05:16.600
 that parameter a should

102
00:05:16.600 --> 00:05:19.500
 contains or should read the word list,

103
00:05:19.500 --> 00:05:21.400
 which is username.txt.

104
00:05:22.300 --> 00:05:25.900
Parameter B should read passwords.txt.

105
00:05:27.300 --> 00:05:30.500
The attack type that we are going to use is cluster bomb

106
00:05:30.500 --> 00:05:33.900
 and finally the matches condition which is

107
00:05:33.900 --> 00:05:36.500
 and we are going to match a word in

108
00:05:36.500 --> 00:05:39.400
 the body, which is Success that we

109
00:05:39.400 --> 00:05:41.500
 have seen just now over here.

110
00:05:44.200 --> 00:05:47.600
And we should also see a status code of 200. Okay?

111
00:05:48.600 --> 00:05:51.600
Let us see how we can run this template

112
00:05:51.600 --> 00:05:54.600
 and RV able to successfully identify the

113
00:05:54.600 --> 00:05:56.400
 correct username and password.

114
00:05:57.400 --> 00:06:00.100
So I'm going to save this template quickly and go to

115
00:06:00.100 --> 00:06:01.300
 my terminal.

116
00:06:05.500 --> 00:06:08.300
I'm going to specify the target URL which is

117
00:06:08.300 --> 00:06:11.800
 HTTP. Colon slash slash bug Bounty Hunter

118
00:06:11.800 --> 00:06:12.900
 dot org.

119
00:06:13.400 --> 00:06:16.700
I'm going to specify the template as well. So the

120
00:06:16.700 --> 00:06:19.300
 template is over here. I'm going to drag and

121
00:06:19.300 --> 00:06:20.800
 drop this template here.

122
00:06:22.100 --> 00:06:26.600
And then we need to specify hyphen

123
00:06:25.600 --> 00:06:28.500
 P which stands

124
00:06:28.500 --> 00:06:31.800
 for proxy that means I want to see and capture

125
00:06:31.800 --> 00:06:34.800
 this request from burpsuit as

126
00:06:34.800 --> 00:06:35.000
 well.

127
00:06:38.100 --> 00:06:41.600
Let us see with hyphen V flag what exactly happens

128
00:06:41.600 --> 00:06:43.200
 when we run this template.

129
00:06:44.300 --> 00:06:47.300
Now remember when we are running fuzzing, we

130
00:06:47.300 --> 00:06:51.700
 require usernames.txt and passwords.txt that

131
00:06:51.700 --> 00:06:55.000
 we have given in our template. So let's

132
00:06:54.300 --> 00:06:56.600
 create that as well.

133
00:06:58.100 --> 00:07:02.200
So now I'm going to say Nano usernames Dot

134
00:07:01.200 --> 00:07:04.000
 txt. And we are going to

135
00:07:04.400 --> 00:07:06.100
 create a quick word list.

136
00:07:06.800 --> 00:07:08.700
Let's give the password demo.

137
00:07:10.300 --> 00:07:10.900
Tomcat

138
00:07:12.300 --> 00:07:13.100
actify

139
00:07:14.000 --> 00:07:14.400
password

140
00:07:15.600 --> 00:07:17.400
admin Keto

141
00:07:17.900 --> 00:07:18.500
hacker

142
00:07:19.400 --> 00:07:20.100
I love you.

143
00:07:21.300 --> 00:07:24.300
And hacking these are some of the most

144
00:07:24.300 --> 00:07:27.600
 default passwords. Let's copy this file to

145
00:07:27.600 --> 00:07:30.400
 passwords dot txt as well.

146
00:07:30.400 --> 00:07:33.600
 So now we have to files which are over word

147
00:07:33.600 --> 00:07:33.800
 list.

148
00:07:34.400 --> 00:07:35.900
So let's run this template.

149
00:07:36.700 --> 00:07:40.600
now so I'm going to specify nuclei hyphenu

150
00:07:39.600 --> 00:07:42.600
 the target the template that

151
00:07:42.600 --> 00:07:45.800
 we have written just now, which is fuzzing cluster

152
00:07:45.800 --> 00:07:48.100
 Bomb Dot, yml and hyphen V

153
00:07:49.100 --> 00:07:53.300
Now let us also read quickly the username.txt file.

154
00:07:54.400 --> 00:07:57.400
Oops, let's let's read the

155
00:07:57.400 --> 00:08:00.800
 username.txt file and we have similarly a

156
00:08:00.800 --> 00:08:03.800
 password dot txt file as well. So we

157
00:08:03.800 --> 00:08:06.800
 are going to use these two word list for fuzzing.

158
00:08:10.800 --> 00:08:13.100
Let's hit enter and let us see the

159
00:08:13.100 --> 00:08:16.500
 output as you can see over here. The fuzzing has

160
00:08:16.500 --> 00:08:19.400
 started successfully. The first request has been

161
00:08:19.400 --> 00:08:22.700
 sent and you can see in the username demo was

162
00:08:22.700 --> 00:08:25.000
 used as a username and password demo.

163
00:08:25.700 --> 00:08:29.400
In the username Tomcat demo hackify and

164
00:08:28.400 --> 00:08:32.600
 password as demo username

165
00:08:31.600 --> 00:08:34.900
 password and password as demo

166
00:08:34.900 --> 00:08:37.900
 and so on so you can see this is

167
00:08:37.900 --> 00:08:40.500
 because of the cluster bomb technique that

168
00:08:40.500 --> 00:08:43.900
 we are using enrich. We are keeping one payload position

169
00:08:43.900 --> 00:08:46.700
 as fixed and reiterating the second one.

170
00:08:47.500 --> 00:08:50.500
So let's wait for this to complete and you

171
00:08:50.500 --> 00:08:53.300
 can see in between itself. You are successfully

172
00:08:53.300 --> 00:08:56.800
 able to match and get the output over

173
00:08:56.800 --> 00:08:59.500
 here where in the username supplied is admin

174
00:08:59.500 --> 00:09:03.700
 and the password supplied is also admin over

175
00:09:02.700 --> 00:09:05.700
 here, which is the parameter a

176
00:09:05.700 --> 00:09:08.600
 and parameter B. Absolutely, correct.

177
00:09:08.600 --> 00:09:11.500
 Let us stop this and let's run this once

178
00:09:11.500 --> 00:09:13.600
 more without hyphen V.

179
00:09:14.900 --> 00:09:17.500
So this will keep on running the cluster bomb

180
00:09:17.500 --> 00:09:20.700
 fuzzing in the background for the parameter a

181
00:09:20.700 --> 00:09:24.100
 and parameter B, which is basically username and

182
00:09:23.100 --> 00:09:26.200
 password with our two word

183
00:09:26.200 --> 00:09:30.000
 list that we have created. Once it identifies that

184
00:09:29.500 --> 00:09:33.300
 the username password has correctly worked.

185
00:09:34.100 --> 00:09:38.000
based on the matcher condition that we have written which is Success it

186
00:09:37.200 --> 00:09:39.500
 will give us the output that

187
00:09:40.300 --> 00:09:41.200
result found

188
00:09:42.100 --> 00:09:45.600
as you can see on your screen right now, you are successfully

189
00:09:45.600 --> 00:09:48.200
 able to identify the correct username and

190
00:09:48.200 --> 00:09:49.000
 password.

191
00:09:50.100 --> 00:09:52.000
I hope you guys understood this. Thank you.
