WEBVTT - This file was automatically generated by VIMEO

0
00:00:14.300 --> 00:00:16.600
Hello everyone and welcome to this lesson.

1
00:00:17.700 --> 00:00:20.300
So now we are going to identify and see

2
00:00:20.300 --> 00:00:23.500
 how nuclear I was able to detect that the

3
00:00:23.500 --> 00:00:27.500
 target is running nginx version, which is 1.19.0.

4
00:00:29.300 --> 00:00:32.800
To do that I can see the specific template that was

5
00:00:32.800 --> 00:00:35.400
 used for detecting the nginx version.

6
00:00:36.400 --> 00:00:39.700
So I'm going to run that specific template only which is

7
00:00:39.700 --> 00:00:41.700
 inside the Technologies path.

8
00:00:43.300 --> 00:00:46.600
Let's go ahead and see the nginx version template

9
00:00:46.600 --> 00:00:49.300
 which can be seen over here nginx version

10
00:00:49.300 --> 00:00:50.500
 Dot yaml.

11
00:00:51.700 --> 00:00:55.000
I'm going to specify hyphen debug and hyphen

12
00:00:54.200 --> 00:00:56.200
 V and hit enter.

13
00:00:58.600 --> 00:01:01.200
By specifying hyphen debug. I am able

14
00:01:01.200 --> 00:01:04.300
 to see exactly what is the HTTP request that

15
00:01:04.300 --> 00:01:07.900
 has been sent to the Target. And what is the HTTP response

16
00:01:07.900 --> 00:01:09.900
 that has been received from the target?

17
00:01:12.500 --> 00:01:15.800
Let me scroll up and let's inspect the HTTP

18
00:01:15.800 --> 00:01:16.400
 request first.

19
00:01:17.700 --> 00:01:20.400
You can see HTTP get based request was

20
00:01:20.400 --> 00:01:23.500
 sent you can also read it from here. HTTP request sent

21
00:01:23.500 --> 00:01:24.700
 for that specific Target.

22
00:01:26.700 --> 00:01:29.400
We can see we received a 200 okay response which

23
00:01:29.400 --> 00:01:32.600
 has been highlighted due to the template which

24
00:01:32.600 --> 00:01:34.500
 we are going to quickly look right now.

25
00:01:35.900 --> 00:01:41.000
You can also see the server is nginx 1.19.0

26
00:01:38.000 --> 00:01:41.400
 so

27
00:01:41.400 --> 00:01:45.200
 we can confirm from here now that the HTTP response

28
00:01:44.200 --> 00:01:47.600
 that has been received from this specific Target

29
00:01:47.600 --> 00:01:51.700
 contains the engine X version 1.19.0 which

30
00:01:51.700 --> 00:01:53.600
 has been identified and given us.

31
00:01:54.700 --> 00:01:57.500
You can also see there are two things which have

32
00:01:57.500 --> 00:02:00.500
 been highlighted over here. The first is the status which

33
00:02:00.500 --> 00:02:03.500
 is the status code which was matched which is 200. Okay

34
00:02:03.500 --> 00:02:06.900
 and a regex1 which is nginx version

35
00:02:06.900 --> 00:02:09.000
 1.19.0.

36
00:02:11.200 --> 00:02:14.400
Let us go on the Target and let us quickly go

37
00:02:14.400 --> 00:02:15.300
 to the inspect.

38
00:02:16.300 --> 00:02:19.200
Let's go to the network Tab and reload this target.

39
00:02:20.600 --> 00:02:23.300
Let's click on the first request and let's try to

40
00:02:23.300 --> 00:02:26.200
 inspect the request and the response that has been

41
00:02:26.200 --> 00:02:26.300
 sent.

42
00:02:28.400 --> 00:02:31.500
Here you can see the request headers and here you can see the response

43
00:02:31.500 --> 00:02:32.200
 headers as well.

44
00:02:33.200 --> 00:02:36.800
If you look very carefully you can see the exact same information can

45
00:02:36.800 --> 00:02:38.300
 be found here as well.

46
00:02:39.100 --> 00:02:43.900
That means nuclei was successfully able to identify nginx

47
00:02:42.900 --> 00:02:45.600
 version from the header which

48
00:02:45.600 --> 00:02:48.900
 is server and was able to Rejects and

49
00:02:48.900 --> 00:02:52.400
 extract the exact version which is 1.19.0

50
00:02:51.400 --> 00:02:54.700
 which gives us the output in front

51
00:02:54.700 --> 00:02:56.600
 of our screen as can. We seen over here.

52
00:02:58.400 --> 00:03:01.500
We are going to understand how nuclei did

53
00:03:01.500 --> 00:03:04.500
 this with the help of the template which is nginx version

54
00:03:04.500 --> 00:03:07.100
 dot yaml in the

55
00:03:07.100 --> 00:03:08.300
 future course of action.

56
00:03:09.100 --> 00:03:13.100
Wherein we are also going to understand that how you can also modify

57
00:03:12.100 --> 00:03:15.800
 these templates and write your own templates

58
00:03:15.800 --> 00:03:19.100
 for matching more specific reach

59
00:03:18.100 --> 00:03:21.500
 access from the HTTP response that

60
00:03:21.500 --> 00:03:22.700
 you get from your target.

61
00:03:24.300 --> 00:03:26.300
So that's it for this lesson. Thank you.
