WEBVTT - This file was automatically generated by VIMEO

1
00:00:08.300 --> 00:00:11.300
 Everyone, welcome back. Let's take a look at you

2
00:00:11.300 --> 00:00:14.300
 to be session hijacking. Yep years. They

3
00:00:14.300 --> 00:00:17.300
 looked at the difference between UDP and TCP protocol. So

4
00:00:17.300 --> 00:00:20.600
 unlike PCP is no correct connection orientation, in

5
00:00:20.600 --> 00:00:23.400
 such a way that we don't track back as

6
00:00:23.400 --> 00:00:26.700
 two. Three Co has been delivered. So, there is no need for any sequence number.

7
00:00:26.800 --> 00:00:27.900
 In this particular protocol.

8
00:00:28.800 --> 00:00:31.500
 So, what really makes you to be vulnerable? Is

9
00:00:31.500 --> 00:00:35.000
 that since there is no sequence of and shaking. So

10
00:00:34.200 --> 00:00:38.100
 the protocol itself will not use

11
00:00:37.200 --> 00:00:40.500
 multiple lessee, key iconic

12
00:00:40.500 --> 00:00:43.300
 numbers so that the attacker doesn't need to force

13
00:00:43.300 --> 00:00:46.500
 them all of these. Now, in this part of the demo,

14
00:00:46.600 --> 00:00:49.700
 it be taking, we look at a very basic example

15
00:00:49.100 --> 00:00:51.700
 of UDP connection. Now, tie gentle

16
00:00:54.700 --> 00:00:56.400
 So, let's assume that.

17
00:01:39.400 --> 00:01:41.600
 I see the connection was established.

18
00:01:55.200 --> 00:01:58.100
 So, we see that the connection was established and we were able to send the

19
00:01:58.100 --> 00:01:58.700
 messages.

20
00:02:00.100 --> 00:02:03.300
 Now, the tool that we are going to use currently is known

21
00:02:03.300 --> 00:02:06.300
 as Steppy or python. So

22
00:02:06.300 --> 00:02:09.300
 this is a python-based package, Android do that.

23
00:02:09.300 --> 00:02:10.000
 We'll be using

24
00:02:12.800 --> 00:02:15.300
 So once this particular library is

25
00:02:15.500 --> 00:02:18.300
 enabled, let's go ahead and create a normal IP

26
00:02:18.300 --> 00:02:18.800
 packet.

27
00:02:33.900 --> 00:02:36.100
 Now, let's go ahead and create an IP packet.

28
00:02:44.100 --> 00:02:46.100
 We're going to provide the destination IP.

29
00:02:59.200 --> 00:03:03.300
 So now we're bored. You also going to add the

30
00:03:02.400 --> 00:03:05.300
 source port.

31
00:03:06.500 --> 00:03:08.800
 And the source IP as well.

32
00:03:24.800 --> 00:03:27.800
 So, let's create the additional duty P protocol details.

33
00:03:58.100 --> 00:04:01.300
 We also need to specify the soul that you're trying to force. In.

34
00:04:01.300 --> 00:04:04.500
 This case, will be the victim Port that's being company.

35
00:04:04.200 --> 00:04:07.600
 So if we go back, we see that particular

36
00:04:07.600 --> 00:04:11.100
 Port, 638 680 support

37
00:04:10.200 --> 00:04:13.200
 that has been used by the victim. So

38
00:04:13.200 --> 00:04:15.400
 we need to add that as a source phone.

39
00:04:30.600 --> 00:04:31.700
 So let's create a piano.

40
00:04:41.700 --> 00:04:44.200
 We need to compile the packet that

41
00:04:44.200 --> 00:04:47.600
 could contain all the information of the IP along with

42
00:04:47.700 --> 00:04:50.000
 UTP details and the payload.

43
00:05:00.200 --> 00:05:03.500
 Just look at the packet that we have constructed.

44
00:05:12.400 --> 00:05:15.400
 So as we can, look at this, what you're trying to achieve like radiant

45
00:05:15.400 --> 00:05:18.400
 a packet was that we are trying to spoof as the

46
00:05:18.400 --> 00:05:21.300
 victim who's going to to the server. So hence a source IP

47
00:05:21.300 --> 00:05:24.400
 would be the victims, IP and the destination

48
00:05:24.400 --> 00:05:27.100
 would be the server. And we have also specified the

49
00:05:27.100 --> 00:05:30.400
 servers for that is opened and the current connection that

50
00:05:30.400 --> 00:05:33.100
 is being established from the victim. And the

51
00:05:33.100 --> 00:05:35.600
 payload that we are going to send this your hat.

52
00:05:36.500 --> 00:05:38.000
 Let's go ahead and send them back.

53
00:05:44.100 --> 00:05:47.500
 As we can see the packet was sent and we can see,

54
00:05:47.200 --> 00:05:50.300
 we have spooked a packet saying that

55
00:05:50.300 --> 00:05:53.600
 from the victim's open port and

56
00:05:53.600 --> 00:05:56.500
 the IP. We are able to send a

57
00:05:56.500 --> 00:05:57.800
 hijacking, the session video.

58
00:05:59.900 --> 00:06:02.200
 This is related to the scenario and

59
00:06:02.200 --> 00:06:05.600
 like TCP. The UDP protocol is

60
00:06:05.600 --> 00:06:08.400
 not going to wait for a handshake. So once a

61
00:06:08.400 --> 00:06:11.400
 so blind sensor request

62
00:06:11.400 --> 00:06:14.900
 to the server, now the Subways

63
00:06:14.900 --> 00:06:17.600
 go to bombard back with the responses. So in this project is

64
00:06:17.700 --> 00:06:20.300
 we can forge either the victim or the server by

65
00:06:20.300 --> 00:06:22.700
 using this particular knowledge.

66
00:06:23.800 --> 00:06:25.300
 That's it for this video. Thank you.
