WEBVTT - This file was automatically generated by VIMEO

0
00:00:04.300 --> 00:00:08.100
So in this lesson, we are going to understand about unsafe

1
00:00:07.100 --> 00:00:10.300
 HTTP draw request as we

2
00:00:10.300 --> 00:00:13.200
 have already seen raw request. We will now

3
00:00:13.200 --> 00:00:15.600
 see what are unsafe raw requests.

4
00:00:16.600 --> 00:00:19.400
So these unsafe raw requests

5
00:00:19.400 --> 00:00:22.400
 are used for complete control and customization of

6
00:00:22.400 --> 00:00:25.500
 the request that we are going to send to the

7
00:00:25.500 --> 00:00:27.100
 bug Bounty programs Target.

8
00:00:27.900 --> 00:00:30.700
This allows us to use any kind

9
00:00:30.700 --> 00:00:33.700
 of malformed request as well. This can

10
00:00:33.700 --> 00:00:36.800
 be super useful. If you are trying to approach

11
00:00:36.800 --> 00:00:40.900
 for finding one probabilities like crlf

12
00:00:39.900 --> 00:00:43.000
 or HTTP request

13
00:00:42.900 --> 00:00:44.300
 smuggling as well.

14
00:00:45.400 --> 00:00:49.500
We can enable this by using unsafe colon

15
00:00:48.500 --> 00:00:51.300
 true through which nuclei will

16
00:00:51.300 --> 00:00:55.000
 automatically understand that we are trying to send an unsafe

17
00:00:54.700 --> 00:00:56.000
 raw request.

18
00:00:57.200 --> 00:01:01.000
So in the Practical time, let's quickly jump on the

19
00:01:00.600 --> 00:01:03.200
 template and see how it can be written.

20
00:01:05.200 --> 00:01:08.800
So you can see I have written an unsafe raw request.yml template

21
00:01:08.800 --> 00:01:11.600
 provided the ID block info block

22
00:01:11.600 --> 00:01:14.100
 request raw. We are

23
00:01:14.100 --> 00:01:17.300
 going to send the same request once again, but this time

24
00:01:17.300 --> 00:01:20.400
 in the header we have specified that we are sending

25
00:01:20.400 --> 00:01:22.500
 an unsafe HTTP request.

26
00:01:23.300 --> 00:01:27.400
And you can also see I have enabled the unsafe colon

27
00:01:26.400 --> 00:01:29.400
 true flag as well.

28
00:01:30.500 --> 00:01:32.800
Alright, so let's send this request quickly.

29
00:01:39.500 --> 00:01:42.100
I'm going to remove the raw request and I'm

30
00:01:42.100 --> 00:01:42.800
 going to save.

31
00:01:44.100 --> 00:01:47.400
And I'm going to send an unsafe raw request this time and hit

32
00:01:47.400 --> 00:01:47.900
 enter.

33
00:01:51.600 --> 00:01:52.800
Let's go to perp suit.

34
00:01:53.700 --> 00:01:56.800
And you can see we have received the unsafe raw

35
00:01:56.800 --> 00:01:57.600
 request as well.

36
00:01:58.800 --> 00:02:01.000
As you can see over here. We are trying to

37
00:02:01.200 --> 00:02:02.200
 send a post request.

38
00:02:02.900 --> 00:02:05.400
With the method as post that we

39
00:02:05.400 --> 00:02:06.500
 can confirm from here.

40
00:02:07.500 --> 00:02:10.200
And we can also see you're sending a request to

41
00:02:10.200 --> 00:02:13.400
 a specific endpoint post with a custom

42
00:02:13.400 --> 00:02:16.800
 header, which is actify header hectify unsafe

43
00:02:16.800 --> 00:02:19.200
 HTTP search equals to Apple in the

44
00:02:19.200 --> 00:02:19.600
 body.

45
00:02:20.600 --> 00:02:23.800
And you can see we got an error it says bad request

46
00:02:23.800 --> 00:02:26.300
 because this is an unsafe fraud request

47
00:02:26.300 --> 00:02:29.500
 that we have created. As I said previously this

48
00:02:29.500 --> 00:02:32.900
 can be super useful in identifying requests smuggling or

49
00:02:32.900 --> 00:02:35.500
 CRF based issues.

50
00:02:36.200 --> 00:02:36.600
Thank you.
