WEBVTT - This file was automatically generated by VIMEO

0
00:00:03.700 --> 00:00:06.400
Hello everyone and welcome to this lesson.

1
00:00:07.800 --> 00:00:10.800
So now we are going to understand about nuclei traffic

2
00:00:10.800 --> 00:00:11.400
 tagging.

3
00:00:12.400 --> 00:00:15.500
It is very very important for the bug

4
00:00:15.500 --> 00:00:17.400
 Bounty programs as well to know.

5
00:00:18.300 --> 00:00:21.500
What specific traffic you are sending to what program?

6
00:00:22.500 --> 00:00:25.700
It becomes essential sometime to identify

7
00:00:25.700 --> 00:00:29.200
 and track down your request that you might have sent while

8
00:00:28.200 --> 00:00:31.700
 you are trying to exploit a

9
00:00:31.700 --> 00:00:32.700
 specific vulnerability.

10
00:00:34.200 --> 00:00:37.800
This also helps to track if you identified

11
00:00:37.800 --> 00:00:40.900
 a vulnerability but is not reproducible at

12
00:00:40.900 --> 00:00:43.700
 a point of time the program manager or

13
00:00:43.700 --> 00:00:46.500
 the treasure can still know that you

14
00:00:46.500 --> 00:00:49.100
 are the one who successfully exploited it once

15
00:00:49.900 --> 00:00:51.000
from the requests

16
00:00:52.900 --> 00:00:55.600
so you can use nuclei traffic tagging

17
00:00:55.600 --> 00:00:58.700
 feature that can be super useful and I recommend everyone to

18
00:00:58.700 --> 00:00:59.100
 do that.

19
00:01:00.700 --> 00:01:03.200
You can set your custom traffic using the

20
00:01:03.200 --> 00:01:05.600
 flag hyphen H or header.

21
00:01:06.500 --> 00:01:09.700
One of the example has been shown over here, which is I'm supplying

22
00:01:09.700 --> 00:01:12.700
 a custom header called as user agent

23
00:01:12.700 --> 00:01:14.400
 mozilla-actify.

24
00:01:15.500 --> 00:01:18.200
So it's a practical time and let us see

25
00:01:18.200 --> 00:01:21.600
 how you can do this and implement it practically.

26
00:01:23.900 --> 00:01:27.000
Before we do that. Let's see this Yahoo! Bug

27
00:01:26.300 --> 00:01:28.500
 Bounty program on hacker 1

28
00:01:29.700 --> 00:01:31.500
Yeah, you can see they have clearly mentioned.

29
00:01:32.700 --> 00:01:35.200
Please include a custom HTTP header in

30
00:01:35.200 --> 00:01:35.900
 all your traffic.

31
00:01:36.900 --> 00:01:39.600
Burp another proxies allow this to

32
00:01:39.600 --> 00:01:40.900
 be done automatically.

33
00:01:42.200 --> 00:01:45.100
Report us what header you have set so we can

34
00:01:45.100 --> 00:01:48.300
 identify the outbound request from

35
00:01:48.300 --> 00:01:51.100
 your system that has been received by the bug Bounty program.

36
00:01:52.800 --> 00:01:56.000
And many other bug bonding programs as well request you

37
00:01:55.100 --> 00:01:58.700
 to do that. So it becomes easy for them to

38
00:01:58.700 --> 00:02:01.400
 identify your request based on

39
00:02:01.400 --> 00:02:02.100
 traffic tagging.

40
00:02:03.800 --> 00:02:06.600
You can see here. You can specify the identifier as

41
00:02:06.600 --> 00:02:09.500
 your username in the format, which is X bug

42
00:02:09.500 --> 00:02:10.100
 Bounty header.

43
00:02:10.800 --> 00:02:13.100
Hacker one and the specific username that you are

44
00:02:13.100 --> 00:02:13.400
 using.

45
00:02:15.400 --> 00:02:18.200
You can also use a unique identifier like a

46
00:02:18.200 --> 00:02:21.500
 chart of 56 Hash a unique identifier or

47
00:02:21.500 --> 00:02:22.800
 a tool name that you are using.

48
00:02:24.100 --> 00:02:27.900
Let us see the same thing that how you can do with the help of nuclei.

49
00:02:29.900 --> 00:02:32.500
Now to check this I'm going to use a request

50
00:02:32.500 --> 00:02:36.300
 catcher, which is ADD bug bounty.requestcatcher.com.

51
00:02:36.900 --> 00:02:39.300
All of you can use this resource free of cost.

52
00:02:40.500 --> 00:02:43.600
Now this is a demo server, which is waiting to

53
00:02:43.600 --> 00:02:46.500
 receive request whenever we try to interact with

54
00:02:46.500 --> 00:02:46.700
 this.

55
00:02:48.400 --> 00:02:51.300
I'm going to go quickly to my terminal and I'm going to send a

56
00:02:51.300 --> 00:02:52.300
 request here now.

57
00:02:57.600 --> 00:03:00.500
Let's say we send a request which is test and

58
00:03:00.500 --> 00:03:01.100
 hit enter.

59
00:03:03.400 --> 00:03:06.200
You can see request was caught successfully. Let's go

60
00:03:06.200 --> 00:03:09.600
 back here. Click on the request that has been caught currently.

61
00:03:11.100 --> 00:03:14.400
You can see the request came to a test endpoint and the

62
00:03:14.400 --> 00:03:18.500
 user agent that was used was curled 7.84.0.

63
00:03:19.400 --> 00:03:21.800
This is the user agent which was sent by curl.

64
00:03:24.900 --> 00:03:27.400
Now let's do the same thing with the help of nuclear as

65
00:03:27.400 --> 00:03:27.500
 well.

66
00:03:28.400 --> 00:03:30.400
So I'm going to specify the URL currently.

67
00:03:31.300 --> 00:03:34.500
Let's say we send a request to a new endpoint which is test one.

68
00:03:36.600 --> 00:03:39.300
We use a specific template that we want to send because we

69
00:03:39.300 --> 00:03:41.300
 do not want to send a lot of requests this time.

70
00:03:43.200 --> 00:03:47.000
So let's use the same template which is inside the Technologies.

71
00:03:47.800 --> 00:03:49.500
nginx nginx

72
00:03:50.100 --> 00:03:52.300
version Dot. Yml.

73
00:03:54.400 --> 00:03:57.100
We are also going to specify a header that we are going to use right now.

74
00:03:59.500 --> 00:04:00.500
Let's say the

75
00:04:01.700 --> 00:04:03.400
header b a user agent

76
00:04:05.500 --> 00:04:05.900
let's say

77
00:04:06.800 --> 00:04:07.700
Mozilla

78
00:04:08.600 --> 00:04:11.300
and let's keep something custom over here. Let's say

79
00:04:11.300 --> 00:04:14.300
 hackify underscore hacker is

80
00:04:14.300 --> 00:04:15.400
 testing currently the target.

81
00:04:16.800 --> 00:04:19.200
All looks good. I'm going to send a request right

82
00:04:19.200 --> 00:04:19.300
 now.

83
00:04:20.100 --> 00:04:23.800
So nuclei is running the template right now, which is nginx version

84
00:04:23.800 --> 00:04:26.500
 dot yml with a custom header that

85
00:04:26.500 --> 00:04:28.800
 we have specified which is hacked if I hacker.

86
00:04:29.500 --> 00:04:33.100
Let's go back over here and see what has happened. You can

87
00:04:33.100 --> 00:04:36.100
 see we have successfully received a request with the

88
00:04:36.100 --> 00:04:40.100
 custom user agent that we supplied which is hackify hacker

89
00:04:39.100 --> 00:04:41.800
 along with the user agent header.

90
00:04:43.100 --> 00:04:46.600
Now this becomes super useful for you that you can tag your

91
00:04:46.600 --> 00:04:49.600
 outbound HTTP traffic which can

92
00:04:49.600 --> 00:04:52.200
 be super useful for bug Bondi program. Try just

93
00:04:52.200 --> 00:04:52.500
 as well.

94
00:04:53.300 --> 00:04:55.800
So I hope you understood how to do this. Thank you.
