WEBVTT - This file was automatically generated by VIMEO

1
00:00:08.100 --> 00:00:11.300
 Hello everyone. Welcome back. As I cover the

2
00:00:11.300 --> 00:00:14.600
 different types of session, hijacking and in-depth, Hands-On

3
00:00:14.800 --> 00:00:17.400
 over. Moral tone model 3, let's

4
00:00:17.400 --> 00:00:19.600
 take an overview about the types.

5
00:00:20.700 --> 00:00:23.300
 So, predominantly all the attacks are

6
00:00:23.300 --> 00:00:26.300
 going to be broken into two main categories. The

7
00:00:26.300 --> 00:00:30.000
 first category is application-level hijacking. So

8
00:00:29.100 --> 00:00:32.200
 when we talk about application hijacking, we are

9
00:00:32.200 --> 00:00:35.400
 going to talk about the web application, which

10
00:00:35.500 --> 00:00:38.100
 runs over HTTP and serves up an

11
00:00:38.100 --> 00:00:39.100
 HTML. Document.

12
00:00:40.200 --> 00:00:43.600
 There are multiple ways and classes of session, hijacking, that

13
00:00:43.600 --> 00:00:45.300
 can be performed against the web.

14
00:00:46.500 --> 00:00:49.200
 Similarly, the second type would

15
00:00:49.200 --> 00:00:52.600
 be the network level in this particular scenario. We

16
00:00:52.600 --> 00:00:55.900
 are talking more about different types of protocol such

17
00:00:55.900 --> 00:00:58.900
 as DNS, TCP, UDP,

18
00:00:58.400 --> 00:00:59.900
 and so on.

19
00:01:01.200 --> 00:01:04.500
 Just to give an overview of the different type of

20
00:01:04.500 --> 00:01:08.000
 attacks, over the web and network. So

21
00:01:07.100 --> 00:01:10.500
 the first one would be man the middle which

22
00:01:10.500 --> 00:01:13.800
 is nothing but the scenario where the

23
00:01:13.800 --> 00:01:16.300
 user is trying to sniff out the

24
00:01:16.300 --> 00:01:19.800
 user session over HTTP session fixation.

25
00:01:19.100 --> 00:01:22.500
 So session fixation is where the attacker actually

26
00:01:22.500 --> 00:01:25.500
 provides a session ID to the user and

27
00:01:25.500 --> 00:01:28.100
 then they pull out the user data back.

28
00:01:29.500 --> 00:01:32.700
 Similarly, we will be looking at something similar

29
00:01:32.300 --> 00:01:35.500
 known as a session ID, brute force in

30
00:01:35.700 --> 00:01:38.800
 which we are trying to actually manipulate

31
00:01:38.800 --> 00:01:41.700
 and generate a session ID, which would be worried

32
00:01:41.700 --> 00:01:44.100
 by the servo and in response. It will

33
00:01:44.100 --> 00:01:47.300
 grant us the permission to take over the session. One

34
00:01:47.300 --> 00:01:50.700
 of such attack, vectors would be cross-site, scripting in

35
00:01:50.700 --> 00:01:53.400
 which will be taking a look at, how

36
00:01:53.400 --> 00:01:56.400
 do we inject JavaScript that dispels a

37
00:01:56.400 --> 00:01:58.700
 JavaScript? Which would in turn?

38
00:01:59.200 --> 00:02:03.000
 Execute a set scripting vectors and

39
00:02:02.300 --> 00:02:05.200
 how do we hijack? Your

40
00:02:05.200 --> 00:02:05.800
 sessions?

41
00:02:07.100 --> 00:02:10.600
 Such intonation is a scenario where the

42
00:02:10.600 --> 00:02:13.200
 attack of for your profile and

43
00:02:13.200 --> 00:02:16.600
 gives you the entire session to the user. Just

44
00:02:16.600 --> 00:02:19.300
 expecting them that they enter some

45
00:02:19.300 --> 00:02:22.500
 sort of data and the attacker can then obtain the

46
00:02:22.500 --> 00:02:25.200
 session, ID itself. So the

47
00:02:25.200 --> 00:02:29.400
 next attack Vector B man-in-the-browser, so

48
00:02:29.400 --> 00:02:32.200
 in which we are talking about malware's that are

49
00:02:32.200 --> 00:02:35.900
 injected and this is just one such attack

50
00:02:35.900 --> 00:02:36.700
 scenario that can.

51
00:02:36.900 --> 00:02:39.100
 Performed by man-in-the-browser and we

52
00:02:39.100 --> 00:02:40.600
 try to hijack. The you session.

53
00:02:41.900 --> 00:02:44.500
 Now, just taking some sort of scenarios over

54
00:02:44.500 --> 00:02:47.200
 the network could be sniffing again in

55
00:02:47.200 --> 00:02:50.600
 which we use tools such as Wireshark. The

56
00:02:50.600 --> 00:02:53.500
 expectation is such that. The attacker is also sitting

57
00:02:53.500 --> 00:02:56.900
 on the same network and is trying to sniff out the network packets

58
00:02:56.300 --> 00:02:59.700
 and identifying the session IDs.

59
00:03:00.800 --> 00:03:03.600
 So, predicting the sequence is also such scenario in

60
00:03:03.600 --> 00:03:06.500
 which we are trying to perform session

61
00:03:06.500 --> 00:03:09.400
 fixation itself in which we are going to

62
00:03:09.400 --> 00:03:13.100
 enumerate and expect application.

63
00:03:12.500 --> 00:03:16.300
 Except the particular scenario will

64
00:03:16.300 --> 00:03:19.400
 also be taking a look at protocol such as UDP and

65
00:03:19.400 --> 00:03:22.300
 how and what tools can be used in order to

66
00:03:22.300 --> 00:03:25.500
 perform. The jean jacket IP spoofing is one,

67
00:03:25.600 --> 00:03:28.500
 such Vector in which an attacker is

68
00:03:28.500 --> 00:03:29.600
 trying to spoof.

69
00:03:30.200 --> 00:03:33.800
 And IP maybe that's how the application or

70
00:03:33.800 --> 00:03:36.200
 the network is being configured. In order to

71
00:03:36.200 --> 00:03:39.300
 accept or authenticates or user based on

72
00:03:39.300 --> 00:03:42.700
 a specific IP. So we will see such Tools

73
00:03:42.100 --> 00:03:45.600
 in which we can use and impersonate another

74
00:03:45.600 --> 00:03:46.500
 usip.

75
00:03:47.700 --> 00:03:51.300
 One such protocol in which we will be taking a look at telnet.

76
00:03:50.700 --> 00:03:53.500
 So we will see the

77
00:03:53.500 --> 00:03:57.100
 type of tools that can be used in order specifically

78
00:03:56.100 --> 00:03:58.800
 to hijack. Telnet sessions.

79
00:04:00.100 --> 00:04:03.300
 And we'll also be taking a look at DNA sessions as well as to

80
00:04:03.300 --> 00:04:06.300
 how does a DNS protocol work and what are the tools that

81
00:04:06.300 --> 00:04:09.600
 are capable enough in order to hijack? A DNS session

82
00:04:09.500 --> 00:04:12.600
 similar to IP spoofing will

83
00:04:12.600 --> 00:04:15.300
 also take a look at the are spoofing in which

84
00:04:15.300 --> 00:04:18.400
 will try to figure out the tools that are capable enough to

85
00:04:18.400 --> 00:04:22.500
 simulate a physical hardware and generate custom

86
00:04:21.800 --> 00:04:24.300
 Hardware addresses, and that

87
00:04:24.300 --> 00:04:27.100
 can be used in order to perform a poisoning.

88
00:04:28.500 --> 00:04:31.700
 And lastly, we also take a look at an SSL strip attack in

89
00:04:31.700 --> 00:04:34.400
 which how an attacker forging a

90
00:04:34.400 --> 00:04:38.000
 network can actually strip out an SSL connection and

91
00:04:37.400 --> 00:04:40.100
 just expecting the

92
00:04:40.100 --> 00:04:44.000
 victim that is already on SSL, secure connection. But

93
00:04:43.300 --> 00:04:46.700
 in reality, these able to sniff out

94
00:04:46.100 --> 00:04:48.700
 the actual traffic in plain text.

95
00:04:50.200 --> 00:04:53.100
 We'll also take a look at the different tools. That would

96
00:04:53.100 --> 00:04:56.400
 be used for our Hands-On sessions as

97
00:04:56.400 --> 00:04:57.800
 for this video. Thank you.
