WEBVTT - This file was automatically generated by VIMEO

1
00:00:08.200 --> 00:00:11.300
 Everyone, let's take a look at the next attack

2
00:00:11.300 --> 00:00:12.700
 known as IP spoofing.

3
00:00:13.900 --> 00:00:16.000
 As an integers is quite clear that the

4
00:00:16.500 --> 00:00:18.100
 attacker is trying to spoof its own IP.

5
00:00:19.600 --> 00:00:22.300
 This particular attack takes advantage of sorts out

6
00:00:22.300 --> 00:00:25.700
 at packets. So technically, an attacker is

7
00:00:25.700 --> 00:00:28.300
 trying to hide the source from where

8
00:00:28.300 --> 00:00:29.800
 the packet is being generated.

9
00:00:30.800 --> 00:00:33.100
 So one of the primary purpose of

10
00:00:33.100 --> 00:00:36.900
 doing so is that the attacker doesn't need to be in between the communication anymore

11
00:00:36.700 --> 00:00:39.500
 as compared to other sessions as

12
00:00:39.700 --> 00:00:40.600
 exacting attacks?

13
00:00:41.700 --> 00:00:44.600
 So one of the reasons this attack is used is

14
00:00:44.600 --> 00:00:47.300
 to hide the source IP in that

15
00:00:47.300 --> 00:00:50.900
 way, an attacker, when performing a heavier attack doesn't

16
00:00:50.900 --> 00:00:53.900
 need to use his own IP, but

17
00:00:53.100 --> 00:00:56.500
 you can always disguise from Battle

18
00:00:56.500 --> 00:00:57.800
 packet is being generated.

19
00:00:58.700 --> 00:01:01.400
 This come on attack is also seen in

20
00:01:01.600 --> 00:01:04.400
 oscillators just because of the purpose of hiding the

21
00:01:04.400 --> 00:01:07.400
 IP. So odd person was

22
00:01:07.400 --> 00:01:10.600
 trying to protect the asset. You would not be able to

23
00:01:10.100 --> 00:01:13.900
 confirm. What's actual Source IP, and

24
00:01:13.900 --> 00:01:16.800
 then attacker can generate multiple Source

25
00:01:16.800 --> 00:01:19.200
 IP addresses in that way. It is very

26
00:01:19.200 --> 00:01:22.500
 difficult for an organization to protect against

27
00:01:22.500 --> 00:01:26.100
 such attacks and one of the other purposes that

28
00:01:25.300 --> 00:01:28.300
 if an attacker wants to send out any

29
00:01:28.500 --> 00:01:32.000
 Just content, you can do so by Heidi's IP again now,

30
00:01:31.500 --> 00:01:34.200
 just, let's take a example.

31
00:01:38.200 --> 00:01:41.600
 So as you can see, I'm using my colleague box in

32
00:01:41.600 --> 00:01:44.500
 order to perform a simple IP spoofing attack.

33
00:01:44.400 --> 00:01:47.900
 So just for us

34
00:01:47.900 --> 00:01:50.700
 to confirm, if the packets are being spoofed.

35
00:01:50.700 --> 00:01:52.100
 I'm going to use y shark.

36
00:01:53.100 --> 00:01:56.500
 So I'm just going to record one

37
00:01:56.500 --> 00:01:58.800
 of the interfaces. That is my local lamb.

38
00:02:01.400 --> 00:02:03.100
 The Pakistani be captured now.

39
00:02:04.600 --> 00:02:07.200
 What I'm going to do is that you using one of the two known

40
00:02:07.200 --> 00:02:08.600
 as H pink tree.

41
00:02:11.300 --> 00:02:14.000
 So this is a syntax error amount. I what I'm

42
00:02:14.300 --> 00:02:17.900
 going to tell is that using this command is

43
00:02:17.400 --> 00:02:20.100
 using H being 3, and

44
00:02:20.100 --> 00:02:23.300
 practice and sing packets or the target address. That

45
00:02:23.300 --> 00:02:25.200
 is 10.00 96.

46
00:02:27.200 --> 00:02:30.300
 As was in the skin types, I'm going to use HP 3 as

47
00:02:30.300 --> 00:02:33.200
 a tool and the parameters are I'm going to pass is I

48
00:02:33.200 --> 00:02:36.800
 finessed which force in attack and

49
00:02:36.800 --> 00:02:39.500
 followed by the Target IP address. That is 10,

50
00:02:39.500 --> 00:02:42.800
 0, 0, 96, and using the I finish, which

51
00:02:42.800 --> 00:02:45.400
 I am going to let know

52
00:02:45.400 --> 00:02:48.200
 what is the spoofed IP address, or I'm going to use. I'm going

53
00:02:48.200 --> 00:02:52.000
 to use one dot 1.1.1 as Source.

54
00:02:51.900 --> 00:02:54.400
 IP that is going to be spooked and

55
00:02:54.400 --> 00:02:56.200
 hyphen C. Switch is going to

56
00:02:57.900 --> 00:03:00.100
 Use let us know the number of packages are going to set.

57
00:03:04.800 --> 00:03:07.500
 As you can see, we have sent three spoofed IP packets.

58
00:03:07.500 --> 00:03:10.100
 Now, let's go back to Wireshark and confirm that.

59
00:03:23.600 --> 00:03:26.500
 Using the IP dot address parameter. I am going to search

60
00:03:26.500 --> 00:03:28.200
 for One Dot. One dot, one dot one.

61
00:03:29.800 --> 00:03:33.100
 Now, as you can see, we have three same

62
00:03:32.100 --> 00:03:35.300
 package that are being sent based on

63
00:03:35.300 --> 00:03:38.500
 the command that we had used. Its - is useful sin

64
00:03:38.500 --> 00:03:41.800
 packets as what we see in each one of those requests and

65
00:03:41.800 --> 00:03:44.100
 the spoof addresses, one dot, one dot, one

66
00:03:44.100 --> 00:03:46.600
 dot one. That is what we see as a suicide pact.

67
00:03:50.300 --> 00:03:53.600
 Just to reiterate a scenario. Actually, that

68
00:03:53.600 --> 00:03:56.500
 article the Senate to be in between the communication Channel,

69
00:03:56.500 --> 00:03:59.600
 unlike other session hijacking scenarios. So

70
00:03:59.800 --> 00:04:03.300
 tracker is going to spoof the IP address of the victim by

71
00:04:03.300 --> 00:04:06.700
 doing so. Specific Network device is

72
00:04:06.700 --> 00:04:09.900
 going to respond back to the victim because during

73
00:04:09.900 --> 00:04:12.200
 the TCP handshake, using the

74
00:04:12.200 --> 00:04:15.200
 source header packets. That is how machine is going to

75
00:04:15.200 --> 00:04:18.600
 know for which so surveys. It has to respond back

76
00:04:18.600 --> 00:04:19.500
 with the communication.

77
00:04:20.100 --> 00:04:23.500
 So just a typical data scenario that occur can

78
00:04:23.500 --> 00:04:26.600
 keep on injecting different packets,

79
00:04:26.800 --> 00:04:29.700
 specifying a specific Source IP

80
00:04:29.100 --> 00:04:32.800
 and forth. At each one of those requests, the

81
00:04:32.800 --> 00:04:34.200
 server is going to respond back.

82
00:04:35.500 --> 00:04:37.000
 That is false video. Thank you.
