WEBVTT - This file was automatically generated by VIMEO

0
00:00:04.300 --> 00:00:07.400
Hi, so in this lesson we are

1
00:00:07.400 --> 00:00:10.600
 going to understand about simple get based

2
00:00:10.600 --> 00:00:11.200
 matcher.

3
00:00:11.900 --> 00:00:14.300
Here we are going to see how you can write

4
00:00:14.300 --> 00:00:18.000
 your quick template that can match something

5
00:00:17.300 --> 00:00:20.600
 in the body of your bug Bounty

6
00:00:20.600 --> 00:00:23.300
 program or the Target that you're going to send a request

7
00:00:23.300 --> 00:00:23.500
 on.

8
00:00:24.800 --> 00:00:27.800
So as you can see on the screen right

9
00:00:27.800 --> 00:00:31.100
 now, here's an sample get paste

10
00:00:30.100 --> 00:00:32.300
 matcher in the body.

11
00:00:33.800 --> 00:00:36.200
Let us see practically how we can

12
00:00:36.200 --> 00:00:37.100
 also do this.

13
00:00:38.300 --> 00:00:41.500
So I have written a template that I'm going to use right now that

14
00:00:41.500 --> 00:00:44.300
 you can see in front of you. I have given the name to

15
00:00:44.300 --> 00:00:47.300
 the template as simple get.yml as you

16
00:00:47.300 --> 00:00:47.900
 can see over here.

17
00:00:48.800 --> 00:00:49.900
This is the ID block.

18
00:00:51.300 --> 00:00:54.500
Next is the info block then the request block which

19
00:00:54.500 --> 00:00:57.700
 says that the request type is get request which

20
00:00:57.700 --> 00:01:01.400
 is going to a specific endpoint, which is nuclei testing

21
00:01:00.400 --> 00:01:02.500
 header.php.

22
00:01:03.200 --> 00:01:06.000
There's a mattress condition and I'm saying I want to

23
00:01:06.200 --> 00:01:10.200
 match a word type and the words is going to be apple the

24
00:01:09.200 --> 00:01:12.500
 condition is and which means there is

25
00:01:12.500 --> 00:01:15.700
 one more matching condition that should be matched for

26
00:01:15.700 --> 00:01:18.400
 a successful output which is a

27
00:01:18.400 --> 00:01:22.200
 status code and the status that I want to match is 200, okay?

28
00:01:23.300 --> 00:01:25.400
Let's save this and let's run this template.

29
00:01:26.400 --> 00:01:29.700
Before we run this let me go to my browser and

30
00:01:29.700 --> 00:01:32.200
 you can see onto this specific endpoint which is

31
00:01:32.200 --> 00:01:35.600
 nuclei testing header.php. There is

32
00:01:35.600 --> 00:01:38.600
 something written which is Apple in the body. So this

33
00:01:38.600 --> 00:01:40.300
 should get matched.

34
00:01:41.700 --> 00:01:42.900
I'm going to quickly run.

35
00:01:43.800 --> 00:01:46.900
Nuclei now with the template

36
00:01:46.900 --> 00:01:49.800
 that we have written on the Target that

37
00:01:49.800 --> 00:01:52.200
 we have just created and we will

38
00:01:52.200 --> 00:01:55.600
 also send this request via the proxy that

39
00:01:55.600 --> 00:01:59.000
 we have configured with burpsuit. I'm

40
00:01:58.200 --> 00:02:01.400
 going to hit enter and let's wait for

41
00:02:01.400 --> 00:02:02.000
 this to run.

42
00:02:02.800 --> 00:02:05.600
You can see the template was

43
00:02:05.600 --> 00:02:08.700
 successfully run without any errors and

44
00:02:08.700 --> 00:02:10.400
 you can see one template was loaded.

45
00:02:11.200 --> 00:02:14.400
We are also able to match this which means this was

46
00:02:14.400 --> 00:02:15.200
 successful.

47
00:02:16.400 --> 00:02:17.500
As you can see over here.

48
00:02:18.500 --> 00:02:20.900
Let's run this once more with hyphen V.

49
00:02:22.300 --> 00:02:25.600
And you can see it was again successful for when

50
00:02:25.600 --> 00:02:27.600
 HTTP request was sent.

51
00:02:28.200 --> 00:02:31.600
Let's go to burp suit and let's see what happened in

52
00:02:31.600 --> 00:02:32.700
 pop suit exactly.

53
00:02:34.100 --> 00:02:37.200
So you can see the latest request that we

54
00:02:37.200 --> 00:02:40.800
 have sent in which you can see HTTP method

55
00:02:40.800 --> 00:02:43.300
 get was used to send a request

56
00:02:43.300 --> 00:02:46.200
 to this specific endpoint and you can see in the

57
00:02:46.200 --> 00:02:49.900
 response apple and we are exactly matching these

58
00:02:49.900 --> 00:02:52.600
 same thing in our template as

59
00:02:52.600 --> 00:02:54.600
 well as can be seen over here.

60
00:02:55.800 --> 00:02:58.200
So I hope you guys understood how you can

61
00:02:58.200 --> 00:03:01.200
 write a quick template in which a simple

62
00:03:01.200 --> 00:03:05.000
 get based matcher can be performed in the body. Thank

63
00:03:04.000 --> 00:03:05.000
 you.
