WEBVTT - This file was automatically generated by VIMEO

0
00:00:06.300 --> 00:00:09.200
Okay guys some welcome back. I hope

1
00:00:09.200 --> 00:00:12.600
 that you liked the content of the course that has been presented so

2
00:00:12.600 --> 00:00:12.800
 far.

3
00:00:13.600 --> 00:00:16.100
And in this video, I'm going to tell you

4
00:00:16.100 --> 00:00:19.500
 more about fuzzing with burp Suite Intruder. It's gonna

5
00:00:19.500 --> 00:00:22.200
 be about tips and tricks. I'm going to

6
00:00:22.200 --> 00:00:26.000
 go into some options of burp

7
00:00:25.200 --> 00:00:28.300
 suit Intruder that I find really helpful.

8
00:00:29.400 --> 00:00:32.200
So let me discuss them right now. I'm gonna

9
00:00:32.200 --> 00:00:36.400
 first focus on request engine which is here. And especially

10
00:00:35.400 --> 00:00:38.800
 I'm going to focus on the throttling.

11
00:00:39.500 --> 00:00:40.500
Throttling is here.

12
00:00:41.900 --> 00:00:45.300
And you know throttling is

13
00:00:44.300 --> 00:00:47.300
 really important when you

14
00:00:47.300 --> 00:00:51.000
 are a Buck Hunter because when you play in

15
00:00:50.300 --> 00:00:53.500
 bug Bounty programs, I very briefly introduced this

16
00:00:53.500 --> 00:00:57.300
 programs in one of the previous videos, then you

17
00:00:56.300 --> 00:00:59.600
 have to obey the rules the companies

18
00:00:59.600 --> 00:01:02.700
 allow you to hack them legally, but

19
00:01:02.700 --> 00:01:05.600
 you have to obey the rules and very often

20
00:01:05.600 --> 00:01:06.900
 one of the rules is like this.

21
00:01:08.100 --> 00:01:11.600
You can use fuzzing provide that you

22
00:01:11.600 --> 00:01:13.800
 are sending one request per second.

23
00:01:14.900 --> 00:01:18.000
The backbounty program owners don't

24
00:01:17.400 --> 00:01:20.400
 want to be overloaded with

25
00:01:20.400 --> 00:01:22.200
 the traffic that you are sending out.

26
00:01:23.100 --> 00:01:26.200
And that's the reason why they want you to

27
00:01:26.200 --> 00:01:27.800
 limit the speed of fuzzing.

28
00:01:28.700 --> 00:01:31.200
And well, you have

29
00:01:31.200 --> 00:01:34.100
 to obey the rules if you don't want to end up

30
00:01:34.100 --> 00:01:34.800
 with problems.

31
00:01:35.500 --> 00:01:38.200
So the natural consequence is that you need to

32
00:01:38.200 --> 00:01:41.400
 go to the settings of burp suit Intruder and you

33
00:01:41.400 --> 00:01:44.900
 need to instruct the birth city Intruder dear burp

34
00:01:44.900 --> 00:01:47.400
 suit Intruder don't send more than

35
00:01:47.400 --> 00:01:49.500
 one request per second. Okay?

36
00:01:51.300 --> 00:01:54.100
You can do it in burp suit Intruder. The problem is that you

37
00:01:54.100 --> 00:01:57.400
 can't do it in a free edition of birth suit

38
00:01:57.400 --> 00:01:57.700
 intruder.

39
00:01:58.300 --> 00:02:01.400
What I've got here is the burp suit free as you

40
00:02:01.400 --> 00:02:05.300
 remember from the previous demos and

41
00:02:04.300 --> 00:02:07.700
 you can see here. I cannot

42
00:02:07.700 --> 00:02:10.600
 edit this things right? I cannot edit

43
00:02:10.600 --> 00:02:13.300
 these things so I cannot play

44
00:02:13.300 --> 00:02:14.200
 with throttling.

45
00:02:15.100 --> 00:02:19.000
I cannot introduce delays in between consecutive

46
00:02:18.700 --> 00:02:21.500
 requests going out from this father

47
00:02:21.500 --> 00:02:24.100
 and I've got a problem how you

48
00:02:24.100 --> 00:02:28.200
 can solve this problem. Well, you can buy for example burp

49
00:02:27.200 --> 00:02:30.500
 suit Pro so professional Edition. I

50
00:02:30.500 --> 00:02:33.800
 really recommend it has a lot of great features that

51
00:02:33.800 --> 00:02:35.000
 are really worth the price.

52
00:02:36.500 --> 00:02:39.300
And as I mentioned a couple of times throughout this

53
00:02:39.300 --> 00:02:42.600
 course, this is really the number one platform for web application

54
00:02:42.600 --> 00:02:45.300
 security testing. So this is really good. But now

55
00:02:45.300 --> 00:02:48.500
 I'm I'm showing you real problem or

56
00:02:48.500 --> 00:02:51.900
 problem challenge that you're gonna have when you

57
00:02:51.900 --> 00:02:54.800
 do a fuzzing in back

58
00:02:54.800 --> 00:02:57.600
 Bounty programs, right? So I'm showing you something really

59
00:02:57.600 --> 00:03:00.600
 realistic and you have to you

60
00:03:00.600 --> 00:03:04.100
 know, keep it in mind when you do fasting so fraught link

61
00:03:03.100 --> 00:03:06.600
 really is really important.

62
00:03:07.700 --> 00:03:10.100
And the next point that I'm

63
00:03:10.100 --> 00:03:11.200
 going to discuss.

64
00:03:11.900 --> 00:03:15.000
Is related to grep much

65
00:03:14.200 --> 00:03:17.600
 functionality and in

66
00:03:17.600 --> 00:03:20.400
 grep much functionality. You can

67
00:03:20.400 --> 00:03:24.300
 just ask the burp

68
00:03:23.300 --> 00:03:26.400
 Suite Intruder to highlight the

69
00:03:26.400 --> 00:03:30.700
 responses that include some keywords. You

70
00:03:29.700 --> 00:03:32.300
 already know that we are talking here about

71
00:03:32.300 --> 00:03:35.900
 requests and responses. We are going to find some

72
00:03:35.900 --> 00:03:38.400
 anomalies in responses and

73
00:03:38.400 --> 00:03:38.900
 stuff like that.

74
00:03:39.800 --> 00:03:43.200
And what will help you in your analysis and

75
00:03:42.200 --> 00:03:45.300
 it is supported in free edition

76
00:03:45.300 --> 00:03:49.200
 of burp a suit is that you can ask burp Suite

77
00:03:48.200 --> 00:03:52.300
 Intruder to highlight the

78
00:03:51.300 --> 00:03:54.800
 responses that include some keywords

79
00:03:54.800 --> 00:03:56.800
 like for example stuck.

80
00:03:57.400 --> 00:04:00.600
Illegal exception error, right when you've

81
00:04:00.600 --> 00:04:03.100
 got this kind of keywords in

82
00:04:03.100 --> 00:04:06.900
 responses like a stock or exception and

83
00:04:06.900 --> 00:04:09.200
 then it means that well most probably

84
00:04:09.200 --> 00:04:12.700
 we've got a stack Trace in the

85
00:04:12.700 --> 00:04:15.200
 response or you've got some exception that

86
00:04:15.200 --> 00:04:19.000
 has been triggered. So it means that basically you are one step

87
00:04:18.500 --> 00:04:21.200
 before finding a vulnerability, right?

88
00:04:21.200 --> 00:04:24.200
 And in other words, it indicates that there

89
00:04:24.200 --> 00:04:27.500
 is probably a vulnerability out there and this

90
00:04:27.500 --> 00:04:30.700
 is a good message for you and you want birth to

91
00:04:30.700 --> 00:04:33.900
 Intruder to inform you about this stuff and

92
00:04:33.900 --> 00:04:36.900
 how to do it. You've got a very nice option

93
00:04:36.900 --> 00:04:38.500
 here. You can click it.

94
00:04:39.400 --> 00:04:43.300
Flag results items with responses matching

95
00:04:42.300 --> 00:04:45.300
 this expressions and that's it.

96
00:04:45.300 --> 00:04:48.900
 Right and then when this is checked, then you

97
00:04:48.900 --> 00:04:52.800
 will see highlighted responses with this

98
00:04:51.800 --> 00:04:54.500
 keywords and it will speed up

99
00:04:54.500 --> 00:04:57.300
 your analysis. You will be more effective in

100
00:04:57.300 --> 00:05:00.900
 finding some anomalies in finding

101
00:05:00.900 --> 00:05:03.200
 vulnerabilities. So this is also what

102
00:05:03.200 --> 00:05:06.400
 I recommend you to do and you can also specify here

103
00:05:06.400 --> 00:05:09.100
 your own keywords, right? You can

104
00:05:09.100 --> 00:05:12.000
 put it here click add and this is it.

105
00:05:12.900 --> 00:05:15.300
So this is very nice and I recommend

106
00:05:15.300 --> 00:05:16.900
 you to play with it as well.

107
00:05:18.200 --> 00:05:21.300
So, okay. So this is it about the tips and tricks that I really

108
00:05:21.300 --> 00:05:24.500
 find useful and I hope

109
00:05:24.500 --> 00:05:27.300
 that this is clear for you. So let me jump to the next video.
