WEBVTT - This file was automatically generated by VIMEO

0
00:00:03.600 --> 00:00:06.400
Hi, so in this lesson we are

1
00:00:06.400 --> 00:00:09.300
 going to learn about raw requests. So what

2
00:00:09.300 --> 00:00:12.500
 are raw requests these are the requests that we

3
00:00:12.500 --> 00:00:15.800
 generally see in our browsers Network

4
00:00:15.800 --> 00:00:18.800
 tab or whenever you capture requests

5
00:00:18.800 --> 00:00:21.600
 using pubsuit or any other proxy tool

6
00:00:21.600 --> 00:00:24.800
 the request are in the format of raw

7
00:00:24.800 --> 00:00:25.100
 request.

8
00:00:26.100 --> 00:00:29.700
Now you can also utilize these raw request

9
00:00:29.700 --> 00:00:31.800
 in your nuclei template as well.

10
00:00:32.600 --> 00:00:35.900
The tool nuclei supports raw request

11
00:00:35.900 --> 00:00:37.500
 to be passed as well.

12
00:00:38.700 --> 00:00:41.800
Raw request can be defined using raw

13
00:00:41.800 --> 00:00:43.800
 column in the nuclei template.

14
00:00:44.700 --> 00:00:48.300
Raw request also supports various helper

15
00:00:47.300 --> 00:00:50.500
 functions that we are going to see in future.

16
00:00:51.600 --> 00:00:54.400
Helper functions can help in manipulation of

17
00:00:54.400 --> 00:00:57.200
 the input for different types of request that you want

18
00:00:57.200 --> 00:00:59.300
 to pass along with the template.

19
00:01:01.200 --> 00:01:04.200
So it's the Practical time and let's quickly see how you

20
00:01:04.200 --> 00:01:06.900
 can specify a raw request in a template.

21
00:01:08.600 --> 00:01:11.800
So as you can see over here, I have written a

22
00:01:11.800 --> 00:01:14.400
 raw request.yeml file that

23
00:01:14.400 --> 00:01:17.700
 you can see over here, which is basically a nuclei

24
00:01:17.700 --> 00:01:19.100
 template of raw request.

25
00:01:20.100 --> 00:01:24.100
This contains the ID block information block the

26
00:01:23.100 --> 00:01:26.300
 request block, which says this time

27
00:01:26.300 --> 00:01:27.200
 as Raw.

28
00:01:28.600 --> 00:01:31.400
then you have to specify it using this way

29
00:01:31.400 --> 00:01:35.500
 in which I'm specifying now the HTTP

30
00:01:34.500 --> 00:01:38.000
 method to be post instead

31
00:01:37.000 --> 00:01:38.400
 of get

32
00:01:39.500 --> 00:01:43.400
Remember, you can also specify any HTTP method.

33
00:01:43.400 --> 00:01:47.500
 It could be get it could be put options patch.

34
00:01:46.500 --> 00:01:49.000
 Delete Etc.

35
00:01:49.800 --> 00:01:53.300
That is basically the sample or

36
00:01:52.300 --> 00:01:56.500
 stock or default raw

37
00:01:55.500 --> 00:01:58.500
 request that you would see anywhere.

38
00:01:59.700 --> 00:02:02.100
Now there are requests. I'm going

39
00:02:02.100 --> 00:02:05.200
 to send a post request to an endpoint

40
00:02:05.200 --> 00:02:08.700
 which is post the host is going to be the host

41
00:02:08.700 --> 00:02:09.100
 name.

42
00:02:10.100 --> 00:02:13.200
A content type header is there and a custom header has

43
00:02:13.200 --> 00:02:17.000
 been added called as hactify header hackify CS

44
00:02:16.200 --> 00:02:19.300
 is the value of the header and in

45
00:02:19.300 --> 00:02:23.000
 the body, we have specified search equals to Apple here.

46
00:02:22.800 --> 00:02:25.300
 If you look carefully we have

47
00:02:25.300 --> 00:02:28.700
 not specified the body colon block

48
00:02:28.700 --> 00:02:31.700
 instead. We have used the entire raw

49
00:02:31.700 --> 00:02:32.200
 request.

50
00:02:32.900 --> 00:02:35.400
Let's see if this and let's run this as

51
00:02:35.400 --> 00:02:36.600
 well on our Target.

52
00:02:38.800 --> 00:02:41.700
This time we are going to modify the current

53
00:02:41.700 --> 00:02:44.400
 template to Raw request.

54
00:02:46.700 --> 00:02:48.200
Dot yml

55
00:02:49.100 --> 00:02:50.800
And I'm going to hit enter.

56
00:02:51.900 --> 00:02:54.700
As we can see we have configured the proxy

57
00:02:54.700 --> 00:02:57.400
 already. Let's go in burpsuit and

58
00:02:57.400 --> 00:02:59.800
 let's see the next request that we have received.

59
00:03:00.700 --> 00:03:03.100
You can see the fourth request contains a

60
00:03:03.100 --> 00:03:05.300
 parameter indeed. So I'm going to click on that.

61
00:03:06.200 --> 00:03:10.100
And if you look carefully this is a post request

62
00:03:09.100 --> 00:03:12.500
 as you can see burp suit

63
00:03:12.500 --> 00:03:15.500
 also shows a raw request, which is

64
00:03:15.500 --> 00:03:18.800
 exactly in the same format that we have supplied using

65
00:03:18.800 --> 00:03:19.700
 nuclei.

66
00:03:20.600 --> 00:03:24.000
We are sending a request to a

67
00:03:23.300 --> 00:03:26.100
 specific endpoint which is post.

68
00:03:27.400 --> 00:03:31.000
you can also see search equals to Apple which

69
00:03:30.200 --> 00:03:33.000
 was a part of our

70
00:03:33.600 --> 00:03:36.200
raw request as can be seen from here.

71
00:03:37.500 --> 00:03:40.100
Once the request has been sent we can

72
00:03:40.100 --> 00:03:44.100
 see we got a response of 404 not found because there

73
00:03:43.100 --> 00:03:46.200
 wasn't any endpoint like post.

74
00:03:47.300 --> 00:03:50.400
But I hope you guys got an idea of how

75
00:03:50.400 --> 00:03:54.200
 nuclei also support sending raw

76
00:03:53.200 --> 00:03:56.700
 request and you can indeed create a

77
00:03:56.700 --> 00:03:59.100
 template of raw request as well. That can

78
00:03:59.100 --> 00:04:00.000
 be super useful.

79
00:04:00.700 --> 00:04:00.900
Thank you.
