WEBVTT - This file was automatically generated by VIMEO

1
00:00:08.200 --> 00:00:11.700
 Hello everyone. Welcome back to this particular slide.

2
00:00:11.200 --> 00:00:15.300
 We'll be taking a look at the next attack work or

3
00:00:15.300 --> 00:00:18.600
 Brute Force as a name. Suggest that

4
00:00:18.600 --> 00:00:21.700
 occur is going to root for secession, IP

5
00:00:21.700 --> 00:00:22.500
 value itself.

6
00:00:23.900 --> 00:00:26.600
 In practice, we have seen scenarios where

7
00:00:26.600 --> 00:00:28.500
 the session IDs are quite random.

8
00:00:30.400 --> 00:00:33.300
 We are taking a look at a scenario where the session

9
00:00:33.300 --> 00:00:36.600
 ID is are having a common pattern.

10
00:00:36.600 --> 00:00:39.400
 Now. Let's take a small example.

11
00:00:42.900 --> 00:00:45.800
 Going back to this particular example, let's

12
00:00:45.800 --> 00:00:48.400
 figure out what is the session ID that

13
00:00:48.400 --> 00:00:50.100
 is being generated for supplication.

14
00:00:54.500 --> 00:00:57.600
 Now as you see the session value is

15
00:00:57.700 --> 00:01:00.300
 2 0, 2 0, 1, 2 0, 0

16
00:01:00.300 --> 00:01:04.300
 1. This is on the Chrome browser. Now.

17
00:01:03.300 --> 00:01:06.500
 I've also initiated a new session

18
00:01:06.700 --> 00:01:09.300
 on Firefox as well. Now. Let's try

19
00:01:09.300 --> 00:01:12.000
 to figure out what is the actual value that has been generated.

20
00:01:16.400 --> 00:01:19.600
 Ask you see this value ends with the digit 6.

21
00:01:21.200 --> 00:01:24.300
 In fact, is an attacker can actually figure out

22
00:01:24.300 --> 00:01:28.400
 a pattern that has been generated for this program. The

23
00:01:28.400 --> 00:01:32.400
 pattern is in the format of yyyy.

24
00:01:31.500 --> 00:01:34.500
 Mmm, followed by

25
00:01:34.600 --> 00:01:37.800
 a three-digit increment value. So,

26
00:01:37.800 --> 00:01:40.500
 an attacker can always understand that

27
00:01:40.500 --> 00:01:43.700
 if he can keep the first six digit

28
00:01:43.700 --> 00:01:46.000
 as constant based on the particular day.

29
00:01:47.800 --> 00:01:50.400
 The calendar year that is this

30
00:01:50.400 --> 00:01:53.300
 is December of 2020. So,

31
00:01:53.300 --> 00:01:56.100
 in that way, he can ensure that the

32
00:01:56.100 --> 00:01:59.200
 first six digits are inconsistent and the,

33
00:01:59.200 --> 00:02:02.200
 last three values could be incremented since so work

34
00:02:02.200 --> 00:02:05.500
 is generating session IDs in sequence with an increment

35
00:02:05.500 --> 00:02:08.500
 of one that could be an assumption. But, however, this

36
00:02:08.500 --> 00:02:11.400
 first six digits are being consistent. So,

37
00:02:11.400 --> 00:02:14.400
 based on this pattern, there are different ways

38
00:02:14.700 --> 00:02:16.700
 of actually creating a

39
00:02:16.900 --> 00:02:19.500
 Food. The first and corn method

40
00:02:19.600 --> 00:02:22.600
 would be to actually send

41
00:02:22.600 --> 00:02:25.600
 manual request to the server, with such an ID

42
00:02:25.400 --> 00:02:29.800
 expecting the value to be correct,

43
00:02:29.800 --> 00:02:32.200
 so that the session can be granted to

44
00:02:32.200 --> 00:02:33.600
 the attacker itself.

45
00:02:35.100 --> 00:02:37.700
 In order to automate, there are multiple ways to do so.

46
00:02:38.800 --> 00:02:41.300
 One of the common ways that occurs do is to write

47
00:02:41.300 --> 00:02:42.100
 some Scripts.

48
00:02:43.500 --> 00:02:46.400
 In this demo will actually take a look at one of the tool.

49
00:02:46.400 --> 00:02:49.300
 For example. Brute force can be done

50
00:02:49.300 --> 00:02:52.600
 by using a tool called Bob sweet. And

51
00:02:52.600 --> 00:02:55.300
 there are committee editions are available for free for

52
00:02:55.300 --> 00:02:56.400
 anyone to download.

53
00:02:57.500 --> 00:03:00.200
 So notice, let's take a look at that.

54
00:03:05.100 --> 00:03:08.700
 As you can see, this is the pope sweet window. So

55
00:03:08.700 --> 00:03:11.400
 what is burp? Suite were sweet is a

56
00:03:11.600 --> 00:03:14.500
 HTTP proxy tool. So that means

57
00:03:14.500 --> 00:03:17.200
 any requests flowing through the browser would be

58
00:03:17.200 --> 00:03:20.100
 captured in this tool first so that we can understand the

59
00:03:20.100 --> 00:03:23.500
 parameters that are being sent to any specific endpoint.

60
00:03:25.300 --> 00:03:28.800
 And based on that during the sting, we can tamper

61
00:03:28.800 --> 00:03:32.500
 different values and send it to the server and

62
00:03:32.500 --> 00:03:35.400
 figure out how the response is going to look. Like. We

63
00:03:35.400 --> 00:03:38.300
 will Deep dive into how it works it works but

64
00:03:38.300 --> 00:03:42.600
 it is something we will be using in this particular tool. So

65
00:03:42.600 --> 00:03:45.100
 what I've done is that I've configured the

66
00:03:45.100 --> 00:03:48.600
 verbs, we tool to work with Firefox. So

67
00:03:48.600 --> 00:03:51.900
 you need to actually set up the proxy on

68
00:03:51.900 --> 00:03:53.700
 the Firefox so that

69
00:03:54.600 --> 00:03:57.300
 All traffic is being rerouted to work sweet tool.

70
00:03:57.700 --> 00:04:00.700
 So the default values would be the Local Host itself. That

71
00:04:00.700 --> 00:04:03.200
 is one 27001 and the

72
00:04:03.200 --> 00:04:06.900
 default port on which both sweet runs is 8080.

73
00:04:06.400 --> 00:04:09.900
 So we are just going to use some basic settings.

74
00:04:11.100 --> 00:04:14.300
 So, the moment I sent a request to the web server. The

75
00:04:14.300 --> 00:04:17.900
 particular request has been captured in this particular screen. Now,

76
00:04:17.900 --> 00:04:20.000
 the request has not been sent to the server yet.

77
00:04:21.100 --> 00:04:24.700
 So as an attacker, what we can do is that you can use multiple

78
00:04:24.900 --> 00:04:27.800
 options. So one of the particular module that

79
00:04:27.800 --> 00:04:30.700
 will be looking at is the Intruder on

80
00:04:30.700 --> 00:04:33.300
 this particular tool. So what I'm going to do, is

81
00:04:33.300 --> 00:04:35.800
 that click on action and send it to intruder.

82
00:04:37.100 --> 00:04:40.200
 So Intruder is module which can

83
00:04:40.200 --> 00:04:43.500
 generate multiple payloads. It could be custom or generated

84
00:04:43.500 --> 00:04:46.300
 by the tool itself. And those data can be

85
00:04:46.300 --> 00:04:48.900
 sent at bulk to the server.

86
00:04:50.700 --> 00:04:53.600
 Now, using Intruder will be taking

87
00:04:53.600 --> 00:04:57.100
 a look at the parameters that are being sent. So

88
00:04:56.100 --> 00:05:00.200
 as you can see the tool as automatically detected

89
00:04:59.200 --> 00:05:02.100
 or numeric value and

90
00:05:02.100 --> 00:05:03.500
 it has been highlighted,

91
00:05:04.500 --> 00:05:07.200
 So, what we'll be doing is that we'll just change this payload.

92
00:05:08.800 --> 00:05:11.600
 So, there are multiple types of payload will

93
00:05:11.600 --> 00:05:13.700
 be using a simple one call numbers.

94
00:05:15.300 --> 00:05:18.300
 Now, we just need to type in the

95
00:05:18.300 --> 00:05:21.500
 values that need to be generated. As we know, the

96
00:05:21.500 --> 00:05:24.400
 format is why why? Why why mmm?

97
00:05:27.200 --> 00:05:30.400
 And the first value be 0, 0 1.

98
00:05:33.100 --> 00:05:36.700
 Now, let's take a scenario where I want to generate

99
00:05:36.700 --> 00:05:39.400
 a sequence till 8.

100
00:05:43.600 --> 00:05:46.400
 Since we understand this being generated in sequence, maybe

101
00:05:46.800 --> 00:05:49.300
 we can just start the attack. And what's

102
00:05:49.300 --> 00:05:52.200
 going to happen with that. Is this going to Brute Force for

103
00:05:52.200 --> 00:05:55.700
 each session ID, starting on the value 0 0, 1 till

104
00:05:55.100 --> 00:05:57.900
 308 with the step of one.

105
00:05:59.900 --> 00:06:01.700
 So just it be similar to attack.

106
00:06:03.600 --> 00:06:06.800
 We see that each session ID as we generated and

107
00:06:06.800 --> 00:06:10.500
 said in sequence. So this is one sort of example, for

108
00:06:10.500 --> 00:06:13.100
 Brute Force. There are multiple ways and

109
00:06:13.100 --> 00:06:16.800
 multiple scenarios where the tiger can use different tools and scripts to

110
00:06:16.200 --> 00:06:17.900
 achieve the same result.

111
00:06:20.100 --> 00:06:23.200
 I'm going back and understanding that I on paper. Let's

112
00:06:23.200 --> 00:06:24.800
 try to read it. The scenario.

113
00:06:25.900 --> 00:06:28.800
 We have a user and a web server, which

114
00:06:28.800 --> 00:06:31.700
 the user is trying to access and the

115
00:06:31.700 --> 00:06:34.200
 same time, the also have an attacker in picture.

116
00:06:36.200 --> 00:06:39.800
 As you can see, the first request is when the user sends

117
00:06:39.800 --> 00:06:42.400
 the request Phillips. So in order to

118
00:06:42.400 --> 00:06:45.300
 generate a session ID, that is the same thing, which

119
00:06:45.300 --> 00:06:49.300
 the attacker is point to do. So in order to understand if

120
00:06:49.300 --> 00:06:52.100
 that's a patent on the session ID, then by

121
00:06:52.100 --> 00:06:55.500
 doing, so he is going to send multiple requests by

122
00:06:55.500 --> 00:06:59.100
 boot forcing the sequence ID of the session and

123
00:06:58.700 --> 00:07:01.300
 expecting that, some of

124
00:07:01.300 --> 00:07:04.500
 the values may actually be valid on the server side. In

125
00:07:04.500 --> 00:07:05.700
 that way, you will be

126
00:07:05.800 --> 00:07:07.400
 Be getting access to the account.

127
00:07:08.800 --> 00:07:10.600
 That's it for this video. Thank you.
