WEBVTT - This file was automatically generated by VIMEO

1
00:00:08.100 --> 00:00:11.400
 Hello everyone, welcome back. So, let's take a look at the

2
00:00:11.400 --> 00:00:12.800
 up whooping attack.

3
00:00:13.900 --> 00:00:16.400
 Options for resolution protocol. Now.

4
00:00:16.400 --> 00:00:19.300
 This is a protocol that all the machines use in

5
00:00:19.300 --> 00:00:22.600
 order to resolve the IP address and a Mac addresses, to

6
00:00:22.600 --> 00:00:25.800
 MAC address is typically the unique address, that

7
00:00:25.800 --> 00:00:28.700
 all the network adapters carry with them. So

8
00:00:28.700 --> 00:00:32.500
 over a local area network connection initially

9
00:00:31.600 --> 00:00:34.700
 whenever we try to connect between computers.

10
00:00:34.700 --> 00:00:37.200
 The particular course is going to check in

11
00:00:37.200 --> 00:00:40.300
 the local our table so that our table. If

12
00:00:40.300 --> 00:00:43.500
 it is called an entry, then it is going to send.

13
00:00:44.100 --> 00:00:47.600
 The data to that specific IP address and the Machine. So

14
00:00:47.600 --> 00:00:51.200
 in order to do that, the apps protocol

15
00:00:50.200 --> 00:00:53.200
 itself is good to broadcast throughout the

16
00:00:53.200 --> 00:00:56.600
 network, seeking the information as to which machine owns

17
00:00:56.600 --> 00:00:59.500
 that particular Hardware at range. So now, let's

18
00:00:59.600 --> 00:01:02.600
 talk about the attack itself. So the attacker is quite

19
00:01:02.100 --> 00:01:05.400
 interested. In performing the attack is because this

20
00:01:05.400 --> 00:01:08.200
 is mainly used in man's ability over a local

21
00:01:08.200 --> 00:01:09.000
 area network.

22
00:01:09.800 --> 00:01:12.400
 And by doing, so what attacker is trying to achieve, is

23
00:01:12.400 --> 00:01:16.500
 that all the traffic is routed through the. So,

24
00:01:16.500 --> 00:01:19.200
 in order to do that. All

25
00:01:19.200 --> 00:01:23.000
 the victims machines will actually be bombarded

26
00:01:22.600 --> 00:01:25.400
 with data to update the

27
00:01:25.400 --> 00:01:28.300
 rock table in such a way, based

28
00:01:28.300 --> 00:01:31.100
 on Doc table. All the data is again going to

29
00:01:31.100 --> 00:01:32.400
 be routed through the attacker.

30
00:01:33.500 --> 00:01:36.400
 So the common reasons why off

31
00:01:36.400 --> 00:01:39.400
 spoofing attack is used is to create do service. For

32
00:01:39.400 --> 00:01:42.300
 example, when an attacker want

33
00:01:42.300 --> 00:01:46.500
 to bombard, a particular machine, then you can update the optical for

34
00:01:46.500 --> 00:01:49.600
 all the other order machines. So

35
00:01:49.600 --> 00:01:52.300
 by doing, so all the machines would

36
00:01:52.300 --> 00:01:55.300
 be confused and rerouting, all the

37
00:01:55.800 --> 00:01:58.400
 traffic to one particular machine resulting in

38
00:01:58.200 --> 00:02:00.200
 pain and of service attacks.

39
00:02:01.800 --> 00:02:04.200
 And now, the common attacks are performing Manda metal

40
00:02:04.200 --> 00:02:07.400
 scenario in a either, too, stiff the data, or to

41
00:02:07.400 --> 00:02:11.200
 hijack, an existing session for a particular protocol.

42
00:02:10.100 --> 00:02:13.200
 Now, let's go ahead

43
00:02:13.200 --> 00:02:14.500
 and look at the demo.

44
00:02:16.200 --> 00:02:19.100
 So let's try to see. What are

45
00:02:19.100 --> 00:02:22.400
 the available network adapters on

46
00:02:22.400 --> 00:02:23.200
 a local machine.

47
00:02:25.400 --> 00:02:28.300
 So by using the, if config command we

48
00:02:28.300 --> 00:02:32.100
 can understand what are the available network adapters? So

49
00:02:31.100 --> 00:02:35.100
 you have you only have one adapter that is eth0 connected

50
00:02:34.400 --> 00:02:37.300
 and other is a loopback adapter.

51
00:02:41.700 --> 00:02:44.500
 Now, in order to figure out the

52
00:02:44.500 --> 00:02:47.500
 exact harder address that is assigned to our local,

53
00:02:47.600 --> 00:02:51.100
 eth0. Let's go and type the command IP

54
00:02:50.100 --> 00:02:51.600
 Link.

55
00:02:55.100 --> 00:02:59.000
 It's by doing. So. We see the particular, ethernet Hardware

56
00:02:58.300 --> 00:03:01.400
 address. That is assigned, that is in form of x.

57
00:03:03.500 --> 00:03:06.200
 Now, let's take a look at the local art table by using the

58
00:03:06.200 --> 00:03:06.900
 arc command.

59
00:03:09.500 --> 00:03:12.100
 So this part of the machine has communicated to all of

60
00:03:12.100 --> 00:03:15.200
 these machines over the network and it

61
00:03:15.200 --> 00:03:18.400
 has a table, which has an existing hardware tools.

62
00:03:18.400 --> 00:03:21.800
 So, whenever this particular machine

63
00:03:21.800 --> 00:03:24.100
 is going to communicate, it is going to

64
00:03:24.100 --> 00:03:27.300
 send to the specific Hardware address that has assigned to this IP

65
00:03:27.300 --> 00:03:27.800
 address.

66
00:03:29.500 --> 00:03:33.000
 Now, let's try and perform mathematical

67
00:03:32.100 --> 00:03:35.400
 props to think so, for this

68
00:03:35.400 --> 00:03:38.200
 particular scenario will be taking a look at one

69
00:03:38.200 --> 00:03:41.100
 of the tool known as either cap.

70
00:03:42.500 --> 00:03:45.400
 This is something that is available in built with

71
00:03:45.400 --> 00:03:46.300
 poly toolkit.

72
00:03:48.600 --> 00:03:52.100
 So the first step would be that by default. It's

73
00:03:51.500 --> 00:03:54.600
 this tool will actually start start

74
00:03:54.700 --> 00:03:57.500
 the network sniffing. So before that, let's

75
00:03:57.500 --> 00:04:00.200
 go ahead and see what are the hosts that

76
00:04:00.200 --> 00:04:03.700
 are available for our Network by going to hose and

77
00:04:03.700 --> 00:04:05.900
 scanning for Rose will get the list.

78
00:04:15.200 --> 00:04:18.100
 So again, going back to host list. We see a

79
00:04:18.100 --> 00:04:19.700
 huge table.

80
00:04:22.400 --> 00:04:25.900
 Letting us know what are the different network devices

81
00:04:25.900 --> 00:04:28.200
 or servers connected to

82
00:04:28.200 --> 00:04:31.800
 particular network with the particular Mac address. Now,

83
00:04:31.300 --> 00:04:35.300
 for this problem, attack. We are taking one.

84
00:04:35.300 --> 00:04:38.100
 Target to be the Gateway in my scenario. It

85
00:04:38.100 --> 00:04:41.400
 is 10001. So this is the router or

86
00:04:41.400 --> 00:04:43.500
 the Gateway that I'm going to address a Target.

87
00:04:45.100 --> 00:04:49.300
 The second pocket would be a specific machine for whom

88
00:04:49.300 --> 00:04:52.700
 we are we are trying to perform Adams attack. So

89
00:04:52.700 --> 00:04:55.300
 my case it is the 96 machine that

90
00:04:55.300 --> 00:04:58.300
 is a Windows machine that is available with the network. I'm

91
00:04:58.300 --> 00:05:00.000
 going to add this as a second target.

92
00:05:01.400 --> 00:05:04.300
 And after doing that, we are going to start the

93
00:05:04.300 --> 00:05:05.000
 ARP poisoning.

94
00:05:06.700 --> 00:05:09.300
 So, when we start out poisoning, we see two

95
00:05:09.300 --> 00:05:12.300
 options, one is to sniff the remote connections. That is something

96
00:05:12.300 --> 00:05:16.500
 that we want in order to gather sensitive data. And

97
00:05:16.500 --> 00:05:19.100
 second is to specify which is about we

98
00:05:19.100 --> 00:05:23.300
 poisoning. That means we just want to broadcast and not them

99
00:05:23.300 --> 00:05:26.500
 to send back the data to us. So since we want all

100
00:05:26.500 --> 00:05:29.400
 the traffic to go through us, we will uncheck this

101
00:05:29.400 --> 00:05:30.200
 second option.

102
00:05:32.200 --> 00:05:34.700
 That's we see the poisoning. Contact us started.

103
00:05:35.800 --> 00:05:38.100
 So now, let's take a normal scenario on

104
00:05:38.100 --> 00:05:39.000
 the victim side.

105
00:05:45.400 --> 00:05:48.500
 So this is a victim who's trying to access a page

106
00:05:48.800 --> 00:05:52.000
 and where there's a login page and the tip might

107
00:05:51.200 --> 00:05:54.900
 fill out any sense information such as username passwords.

108
00:06:00.100 --> 00:06:03.300
 So after the user submits the page, we see that this

109
00:06:03.300 --> 00:06:06.800
 particular tool was automatically able to capture the

110
00:06:06.800 --> 00:06:09.300
 username and a password for a

111
00:06:09.300 --> 00:06:12.300
 particular website that the victim

112
00:06:12.300 --> 00:06:13.100
 was accessing.

113
00:06:14.300 --> 00:06:17.200
 So this is one such scenario home animal attack can

114
00:06:17.200 --> 00:06:20.100
 be performed using our poisoning such that all the

115
00:06:20.100 --> 00:06:23.200
 traffic is sent through that Adam Sheen. This

116
00:06:23.200 --> 00:06:26.400
 retake the scenario. We have an attack to user and

117
00:06:26.400 --> 00:06:29.200
 the server. So initially the

118
00:06:29.200 --> 00:06:32.700
 use of might send a request to the server and

119
00:06:32.700 --> 00:06:35.400
 that occur is trying to spoof the

120
00:06:35.400 --> 00:06:38.700
 hardware address in such a way and both the cases

121
00:06:38.800 --> 00:06:41.500
 that now, the victim and the router

122
00:06:41.500 --> 00:06:43.400
 or the Gateway believe that the

123
00:06:43.500 --> 00:06:46.300
 Need to communicate to that accompany. So in

124
00:06:46.300 --> 00:06:49.600
 such scenario, particular man-in-the-middle attack can

125
00:06:49.600 --> 00:06:52.700
 happen. That's it for this video. Thank

126
00:06:52.700 --> 00:06:52.900
 you.
