WEBVTT - This file was automatically generated by VIMEO

0
00:00:12.900 --> 00:00:15.400
Hi, so in this lesson we

1
00:00:15.400 --> 00:00:17.600
 are going to understand about headers.

2
00:00:18.500 --> 00:00:22.600
How we can specify nuclei templates

3
00:00:22.600 --> 00:00:25.700
 to use custom headers that you want that

4
00:00:25.700 --> 00:00:29.000
 you need to send along with your HTTP traffic

5
00:00:28.500 --> 00:00:31.500
 while you are running nuclei onto any

6
00:00:31.500 --> 00:00:32.400
 bug Bounty program.

7
00:00:33.800 --> 00:00:36.700
So headers can be defined using headers

8
00:00:36.700 --> 00:00:37.400
 colon.

9
00:00:37.900 --> 00:00:41.200
They are placed in a key value format. That

10
00:00:40.200 --> 00:00:43.800
 means example header

11
00:00:43.800 --> 00:00:47.200
 should look something like this, which is user agent

12
00:00:46.200 --> 00:00:50.100
 colon some random user

13
00:00:49.100 --> 00:00:52.800
 agent. You can specify as many

14
00:00:52.800 --> 00:00:55.200
 as headers you want in a specific

15
00:00:55.200 --> 00:00:55.800
 request.

16
00:00:56.500 --> 00:01:00.200
And we know that while we are testing for specific vulnerabilities

17
00:00:59.200 --> 00:01:02.500
 modifying these headers can

18
00:01:02.500 --> 00:01:04.000
 be super useful as well.

19
00:01:05.300 --> 00:01:08.300
So it's the Practical line and let's see how you

20
00:01:08.300 --> 00:01:09.000
 can do it.

21
00:01:11.200 --> 00:01:16.000
I have written a template which is headers.yml that

22
00:01:15.100 --> 00:01:16.600
 you can use.

23
00:01:17.600 --> 00:01:20.900
If you look carefully in this template, we

24
00:01:20.900 --> 00:01:23.900
 have a ID block which says nuclei head

25
00:01:23.900 --> 00:01:26.800
 is block. We have information block, which

26
00:01:26.800 --> 00:01:29.400
 says name as nuclei head is block and other

27
00:01:29.400 --> 00:01:30.100
 basic information.

28
00:01:31.100 --> 00:01:34.900
The request block says the method as get the path

29
00:01:34.900 --> 00:01:37.100
 is the base URL that will be

30
00:01:37.100 --> 00:01:40.700
 taken from the input that we will supply to neatly

31
00:01:40.700 --> 00:01:42.100
 as a Target.

32
00:01:42.900 --> 00:01:45.100
Now this is the important part which is

33
00:01:45.100 --> 00:01:46.100
 the headers.

34
00:01:46.700 --> 00:01:49.400
You can see I have specified the user

35
00:01:49.400 --> 00:01:52.600
 agent as hackedify X forwarded host

36
00:01:52.600 --> 00:01:55.800
 as hackify not in Cache control

37
00:01:55.800 --> 00:01:58.300
 as no transform and I have also

38
00:01:58.300 --> 00:02:01.600
 applied a custom header, which is test header as

39
00:02:01.600 --> 00:02:02.500
 hello world.

40
00:02:03.400 --> 00:02:07.100
Let's save this template that we have just created and pass

41
00:02:06.100 --> 00:02:08.600
 it to nuclear.

42
00:02:11.800 --> 00:02:14.800
This time we are not going to use these.

43
00:02:15.700 --> 00:02:18.100
Old template but instead we are

44
00:02:18.100 --> 00:02:20.700
 going to use the Headless template that we have created.

45
00:02:21.600 --> 00:02:25.300
So I'm going to drop this template over here, and I'm

46
00:02:24.300 --> 00:02:26.200
 going to hit enter.

47
00:02:28.300 --> 00:02:31.300
When I do that the request will pass through

48
00:02:31.300 --> 00:02:34.500
 the proxy as we have already configured the proxy with

49
00:02:34.500 --> 00:02:37.400
 nuclei. So let's go in book and see

50
00:02:37.400 --> 00:02:41.000
 the second request that might have been received that

51
00:02:40.200 --> 00:02:43.000
 we executed just now.

52
00:02:43.900 --> 00:02:47.600
Let me go to the proxy Tab and HTTP history.

53
00:02:48.600 --> 00:02:51.700
You can see this is the second request that we have sent just

54
00:02:51.700 --> 00:02:51.900
 now.

55
00:02:52.900 --> 00:02:53.900
If you look carefully.

56
00:02:56.300 --> 00:02:59.700
Here, this is the request that we have received with

57
00:02:59.700 --> 00:03:00.500
 the get.

58
00:03:01.500 --> 00:03:01.900
method

59
00:03:02.900 --> 00:03:05.000
you can also see the headers that we

60
00:03:05.000 --> 00:03:05.900
 supplied.

61
00:03:06.900 --> 00:03:10.400
You can see X forwarded host as hacktified.in

62
00:03:09.400 --> 00:03:12.700
 test header as hello world

63
00:03:12.700 --> 00:03:15.400
 and cash control as no transform.

64
00:03:15.400 --> 00:03:18.300
 This is exactly the same headers that we

65
00:03:18.300 --> 00:03:21.900
 have written in our headers.yml file

66
00:03:21.900 --> 00:03:24.400
 as a custom template that has

67
00:03:24.400 --> 00:03:25.800
 been sent to the server.

68
00:03:27.300 --> 00:03:29.200
I hope you guys understood this. Thank you.
