WEBVTT - This file was automatically generated by VIMEO

0
00:00:04.200 --> 00:00:07.600
Hi everyone. So in this lesson we are

1
00:00:07.600 --> 00:00:10.800
 going to learn about simple get based

2
00:00:10.800 --> 00:00:13.100
 matches in the header.

3
00:00:14.300 --> 00:00:18.100
As we can see on your screen. We have a sample template

4
00:00:17.100 --> 00:00:21.000
 in which we can see. This is a simple get

5
00:00:20.500 --> 00:00:22.300
 based matcher.

6
00:00:23.100 --> 00:00:26.500
Template which matches something in the header value

7
00:00:26.500 --> 00:00:30.100
 from here as we can see the matches

8
00:00:29.100 --> 00:00:33.200
 condition specify and matches

9
00:00:32.200 --> 00:00:35.500
 type is a word which is Apple which is

10
00:00:35.500 --> 00:00:36.400
 in the header.

11
00:00:37.100 --> 00:00:40.400
And there's a condition and one more which says to match a

12
00:00:40.400 --> 00:00:43.000
 status code, which is 200, okay?

13
00:00:44.300 --> 00:00:47.100
So it is the Practical time and let's quickly see this.

14
00:00:49.400 --> 00:00:52.400
So I have already written a template. So I'm going

15
00:00:52.400 --> 00:00:54.200
 to show you that template real quick.

16
00:00:56.300 --> 00:00:59.200
As you can see over here. This is the template of

17
00:00:59.200 --> 00:01:03.000
 simple get based matcher, which is specified in

18
00:01:02.100 --> 00:01:05.500
 the ID block second block is

19
00:01:05.500 --> 00:01:09.000
 the information block as we can see over here, which

20
00:01:08.300 --> 00:01:11.500
 also specifies the basic detail

21
00:01:11.500 --> 00:01:12.900
 about the template.

22
00:01:13.800 --> 00:01:16.500
the next part is the request Block in which

23
00:01:16.500 --> 00:01:19.600
 we can see we are sending a get based request to

24
00:01:19.600 --> 00:01:22.600
 a path of the base URL that has been supplied

25
00:01:22.600 --> 00:01:26.200
 as a input to a endpoint which is nuclei testing

26
00:01:25.200 --> 00:01:28.600
 header.php and the

27
00:01:28.600 --> 00:01:31.400
 final part of the matches condition with a

28
00:01:31.400 --> 00:01:34.500
 match as condition as and matches type word

29
00:01:34.500 --> 00:01:37.500
 matching Apple, but this time not in

30
00:01:37.500 --> 00:01:40.700
 the body instead in the header and successfully

31
00:01:40.700 --> 00:01:43.200
 matching a status code 200 okay

32
00:01:43.200 --> 00:01:44.700
 to give us output

33
00:01:45.500 --> 00:01:48.700
So let us see this so for testing we're going

34
00:01:48.700 --> 00:01:50.700
 to use this specific Target.

35
00:01:52.200 --> 00:01:55.300
Let's go back to our terminal and let's specify this.

36
00:01:57.600 --> 00:01:57.800
so

37
00:01:58.800 --> 00:02:01.300
we will quickly change our template.

38
00:02:02.900 --> 00:02:05.300
Which is simple get header dot.

39
00:02:05.300 --> 00:02:09.000
 Yml, as you can see we are supplying nuclei

40
00:02:08.700 --> 00:02:11.800
 and the target URL the

41
00:02:11.800 --> 00:02:14.900
 template also have been specified over here and

42
00:02:14.900 --> 00:02:18.600
 we are passing this request wire proxy. We

43
00:02:17.600 --> 00:02:20.400
 can also see we have added a flag

44
00:02:20.400 --> 00:02:23.900
 which is hyphen V with stand for verbose output.

45
00:02:24.700 --> 00:02:25.900
Let's hit enter.

46
00:02:26.600 --> 00:02:29.800
And you can see we were successfully able to match and

47
00:02:29.800 --> 00:02:32.500
 get an output over here, which means

48
00:02:32.500 --> 00:02:35.100
 the matching condition was successful.

49
00:02:35.900 --> 00:02:38.300
Let's quickly go in burp, and let's

50
00:02:38.300 --> 00:02:40.100
 see the request that was sent.

51
00:02:40.800 --> 00:02:43.600
Let's go in the HTTP history and let's pick

52
00:02:43.600 --> 00:02:45.900
 the last request that was sent.

53
00:02:47.600 --> 00:02:50.400
We can see over here are get request is sent nothing

54
00:02:50.400 --> 00:02:51.000
 in the body.

55
00:02:52.400 --> 00:02:55.300
As we can see over here. The header name is

56
00:02:55.300 --> 00:02:58.600
 new header and the value of which is Apple and

57
00:02:58.600 --> 00:03:01.500
 which has been successfully matched. Let's go

58
00:03:01.500 --> 00:03:04.000
 back over here and see we can

59
00:03:04.500 --> 00:03:07.800
 confirm. The matching condition was successful. If

60
00:03:07.800 --> 00:03:10.600
 you also specify hyphen debug you

61
00:03:10.600 --> 00:03:13.700
 would be able to see that as well that Apple has

62
00:03:13.700 --> 00:03:16.100
 been matched successfully in the

63
00:03:16.100 --> 00:03:19.500
 new header value that has been supplied. So

64
00:03:19.500 --> 00:03:22.600
 this template Works, absolutely fine. I'm matching

65
00:03:22.600 --> 00:03:25.500
 the header as well as the status code.

66
00:03:25.500 --> 00:03:28.600
 So I hope you guys understood that how you

67
00:03:28.600 --> 00:03:31.900
 can also write a simple get based matcher

68
00:03:31.900 --> 00:03:34.100
 header template. Thank you.
