WEBVTT - This file was automatically generated by VIMEO

0
00:00:03.600 --> 00:00:06.400
Hello everyone and welcome to this lesson.

1
00:00:07.100 --> 00:00:10.500
As we are understanding about nuclei fuzzing in

2
00:00:10.500 --> 00:00:13.500
 this lesson. We are going to see the second technique which

3
00:00:13.500 --> 00:00:15.200
 is pitch fork.

4
00:00:15.800 --> 00:00:18.700
So what is Pitchfork exactly? It means

5
00:00:18.700 --> 00:00:22.400
 that it rates all the payloads simultaneously

6
00:00:21.400 --> 00:00:23.300
 that means

7
00:00:24.500 --> 00:00:28.200
username first payload from username.txt for

8
00:00:27.200 --> 00:00:30.900
 the password field password from

9
00:00:30.900 --> 00:00:33.900
 the password dot txt file. So

10
00:00:33.900 --> 00:00:36.900
 one by one simultaneously it

11
00:00:36.900 --> 00:00:39.800
 will keep on iterating all the payloads.

12
00:00:40.600 --> 00:00:43.300
So it is the Practical time and let's quickly see

13
00:00:43.300 --> 00:00:46.700
 how we can perform fuzzing using pitchfork.

14
00:00:49.500 --> 00:00:52.200
So I have written a template over here, which is

15
00:00:52.200 --> 00:00:55.600
 fuzzing Pitchfork. This is the info block. Let's

16
00:00:55.600 --> 00:00:57.400
 quickly jump on the request block.

17
00:00:58.500 --> 00:01:01.700
So this is a HTTP raw request a post

18
00:01:01.700 --> 00:01:04.200
 request that can be seen over here, which is going to

19
00:01:04.200 --> 00:01:07.300
 the same endpoint. Nothing has been changed over here.

20
00:01:08.600 --> 00:01:11.900
What has been changed is the attack type? We

21
00:01:11.900 --> 00:01:15.300
 have changed the attack type from cluster

22
00:01:14.300 --> 00:01:17.600
 bomb to Pitchfork and we

23
00:01:17.600 --> 00:01:20.900
 keep the same matching condition as success as

24
00:01:20.900 --> 00:01:23.800
 a word in the body and status

25
00:01:23.800 --> 00:01:25.000
 code AS 200.

26
00:01:26.800 --> 00:01:29.500
Let's go to terminal and let's run

27
00:01:29.500 --> 00:01:31.000
 the same scan.

28
00:01:31.700 --> 00:01:34.200
With the new custom template that

29
00:01:34.200 --> 00:01:37.800
 we have written right now, which is pitchfork.

30
00:01:38.900 --> 00:01:41.200
And let's add hyphen V

31
00:01:41.200 --> 00:01:42.500
 to this and hit enter.

32
00:01:45.900 --> 00:01:48.100
Now you can see the new word list that

33
00:01:48.100 --> 00:01:51.500
 we created has been loaded. The username is demo.

34
00:01:51.500 --> 00:01:54.500
 The password is demo username Tomcat password

35
00:01:54.500 --> 00:01:57.800
 Tomcat username actify password hacktify

36
00:01:57.800 --> 00:02:00.600
 so we can see over here one by

37
00:02:00.600 --> 00:02:05.000
 one. Each username has been taken from the username.txt. Each

38
00:02:04.500 --> 00:02:07.800
 password has been taken from the password Dot txt.

39
00:02:07.800 --> 00:02:10.700
 And the iteration keeps on going simultaneously.

40
00:02:11.600 --> 00:02:14.800
Until it identifies the correct username

41
00:02:14.800 --> 00:02:17.300
 and password as can be seen over here.

42
00:02:18.400 --> 00:02:21.300
So we can see over here. The parameter B is

43
00:02:21.300 --> 00:02:24.400
 admin which is the password and parameter a

44
00:02:24.400 --> 00:02:27.700
 is admin, which is the username which is been successfully found.

45
00:02:29.200 --> 00:02:33.000
Let's run this once more without supplying hyphen

46
00:02:32.100 --> 00:02:35.700
 V and let's wait for the output to complete.

47
00:02:36.900 --> 00:02:39.500
Now it would quickly identify the

48
00:02:39.500 --> 00:02:42.300
 correct username and password while fussing and give

49
00:02:42.300 --> 00:02:44.200
 us the result in this format.

50
00:02:45.400 --> 00:02:48.700
If you want to see what exactly is happening behind

51
00:02:48.700 --> 00:02:51.800
 the hood or you want to capture the request in

52
00:02:51.800 --> 00:02:54.800
 burpsuit as well. You can also do that. So

53
00:02:54.800 --> 00:02:57.500
 I'm going to specify the proxy quickly.

54
00:02:58.600 --> 00:03:01.900
All the requests should pass through my book

55
00:03:01.900 --> 00:03:04.400
 proxy, which is running on 8081.

56
00:03:05.100 --> 00:03:09.000
Now remember each request that would be passed would

57
00:03:08.200 --> 00:03:11.700
 be a username password combination

58
00:03:11.700 --> 00:03:14.500
 simultaneously. Let's hit enter

59
00:03:14.500 --> 00:03:15.900
 and let's go over here.

60
00:03:17.500 --> 00:03:21.100
And you can see continuously request has been sent over here.

61
00:03:22.500 --> 00:03:26.300
Let us pick one of the request and we can see username

62
00:03:25.300 --> 00:03:29.200
 past as hacking password past as

63
00:03:29.200 --> 00:03:32.900
 hacking, which is incorrect username and password, hence.

64
00:03:32.900 --> 00:03:35.400
 We would get a field message.

65
00:03:37.300 --> 00:03:40.600
The correct username is admin and the correct username is

66
00:03:40.600 --> 00:03:43.600
 password which might have been passed in one of the requests

67
00:03:43.600 --> 00:03:44.400
 from here.

68
00:03:45.700 --> 00:03:49.400
So, let's see that as well. You can see in this request admin

69
00:03:48.400 --> 00:03:51.700
 and admin has been passed and the

70
00:03:51.700 --> 00:03:53.000
 result is success.

71
00:03:53.800 --> 00:03:56.600
So this way you can also write a fuzzing

72
00:03:56.600 --> 00:03:59.300
 template based on the attack that we have

73
00:03:59.300 --> 00:04:02.600
 used right now, which is Pitchfork. I hope

74
00:04:02.600 --> 00:04:03.900
 you understood. Thank you.
