WEBVTT - This file was automatically generated by VIMEO

1
00:00:08.200 --> 00:00:11.300
 Hello, welcome back to the second video. Now.

2
00:00:11.400 --> 00:00:14.100
 Let's take a look at a second attack which is known as such in

3
00:00:14.100 --> 00:00:17.700
 fixation. So, in this particular attack, what

4
00:00:17.700 --> 00:00:20.500
 we were trying to do as an attacker is that

5
00:00:20.500 --> 00:00:22.500
 we have a pre-owned session ID.

6
00:00:24.100 --> 00:00:27.000
 And that is something we want to fix on the victim side.

7
00:00:28.300 --> 00:00:31.100
 So now let's try to look at the actual demo and try to

8
00:00:31.100 --> 00:00:32.800
 understand how is it performed?

9
00:00:35.800 --> 00:00:38.300
 As you can see, I have got two different

10
00:00:38.300 --> 00:00:41.600
 browsers open. On the left hand side is a Chrome browser,

11
00:00:41.700 --> 00:00:44.100
 which is an attacker machine. And on

12
00:00:44.100 --> 00:00:47.100
 the right hand side is a Firefox browser, which is on

13
00:00:47.100 --> 00:00:47.600
 the victim.

14
00:00:48.900 --> 00:00:51.500
 So how does this attack actually work?

15
00:00:52.900 --> 00:00:56.100
 The moment. I actually visit this website. I

16
00:00:55.100 --> 00:00:58.500
 have a session ID from

17
00:00:58.500 --> 00:00:59.400
 for myself.

18
00:01:01.300 --> 00:01:04.600
 So if you look at the value, it is starts with 2

19
00:01:04.600 --> 00:01:05.500
 and ends with be.

20
00:01:09.200 --> 00:01:12.900
 So as we looked at the previous attack scenario, we're

21
00:01:12.300 --> 00:01:15.500
 using social engineering that

22
00:01:15.500 --> 00:01:18.500
 occur was able to hijack session. So similarly, in

23
00:01:18.500 --> 00:01:21.400
 the scenario as well. The attacker is going to

24
00:01:21.500 --> 00:01:24.400
 use social medium. In order to

25
00:01:24.400 --> 00:01:26.200
 send this particular token to the user.

26
00:01:28.200 --> 00:01:31.300
 Ideally, the common applications that

27
00:01:31.300 --> 00:01:34.300
 are more vulnerable to the scenario would be, which would have a

28
00:01:34.300 --> 00:01:36.900
 session ID in the URL, get parameter of itself.

29
00:01:38.300 --> 00:01:41.700
 But however, this party application is also vulnerable to

30
00:01:41.700 --> 00:01:44.300
 reflect report site scripting. So

31
00:01:44.300 --> 00:01:48.100
 we can perform the similar attack and instead of hijacking

32
00:01:47.100 --> 00:01:49.900
 the value we can change the value as well.

33
00:01:51.100 --> 00:01:54.600
 So, living apart the social engineering tactics as

34
00:01:54.600 --> 00:01:57.500
 to how the value is being sent out. Now,

35
00:01:57.800 --> 00:02:00.300
 let's assume the fact that the value has been

36
00:02:00.300 --> 00:02:03.700
 provided to the victim. So I'm just using

37
00:02:03.800 --> 00:02:06.900
 an extension called cookie editor or simplicity.

38
00:02:08.300 --> 00:02:11.700
 So we to see that the victim has got a different session.

39
00:02:11.100 --> 00:02:14.200
 So as we spoke to a girl

40
00:02:14.200 --> 00:02:17.200
 is going to provide its own value to the victim.

41
00:02:18.500 --> 00:02:21.200
 So now this is been stored on

42
00:02:21.200 --> 00:02:21.800
 the browser.

43
00:02:23.500 --> 00:02:26.200
 So when the victim will actually you log in using his

44
00:02:26.200 --> 00:02:27.000
 credentials.

45
00:02:32.600 --> 00:02:36.400
 We see that he was able to log in to the administrator panel and

46
00:02:36.900 --> 00:02:39.100
 the cookie value is the

47
00:02:39.100 --> 00:02:42.900
 one that attacker had given to him. So

48
00:02:42.200 --> 00:02:45.300
 that occur in normal scenario, just

49
00:02:45.300 --> 00:02:48.500
 has to wait for the victim to login. So

50
00:02:48.500 --> 00:02:51.800
 now, even without knowing the credentials or

51
00:02:51.800 --> 00:02:54.500
 what is it? That hacker seems he has given

52
00:02:54.900 --> 00:02:57.800
 his own fixed session ID, which

53
00:02:57.800 --> 00:03:00.300
 you wanted the victim to use that's already been set

54
00:03:00.300 --> 00:03:01.300
 up and up and

55
00:03:01.500 --> 00:03:04.300
 Learning and logged in that, I could just go

56
00:03:04.300 --> 00:03:06.100
 back and just refresh the page.

57
00:03:07.500 --> 00:03:10.700
 Now, we see that, just by refreshing the page since

58
00:03:10.900 --> 00:03:13.600
 the cookie was the same and

59
00:03:13.600 --> 00:03:16.400
 it was under revalidated, so we can see

60
00:03:16.400 --> 00:03:18.700
 how session fixation at attack work.

61
00:03:21.700 --> 00:03:23.200
 Just to reiterate the scenario.

62
00:03:24.200 --> 00:03:28.100
 The Tackle will have a legitimate connection initially when

63
00:03:27.100 --> 00:03:30.700
 he's trying to fetch the session ID, which

64
00:03:30.700 --> 00:03:32.200
 he wants the victim to use.

65
00:03:33.200 --> 00:03:36.400
 From that case, it is socially getting tactics which

66
00:03:36.400 --> 00:03:39.300
 would be using either. Why fishing or any

67
00:03:39.300 --> 00:03:42.800
 such methodology to ensure that particular session ID

68
00:03:42.900 --> 00:03:44.900
 is updated on the victim side.

69
00:03:45.900 --> 00:03:49.000
 As soon as I attack, which is on the last video, that

70
00:03:48.100 --> 00:03:51.200
 is cross-site scripting. When that attack can be

71
00:03:51.200 --> 00:03:53.800
 used to ensure that the cookie value is updated.

72
00:03:55.300 --> 00:03:58.200
 And after that, it is just awaitin watch game by

73
00:03:58.200 --> 00:04:01.600
 The Tackle waits for the victim to log in. And

74
00:04:01.900 --> 00:04:04.100
 using the same value. Each is

75
00:04:04.100 --> 00:04:07.200
 refreshes his page. And the session is available, too.

76
00:04:08.500 --> 00:04:12.300
 As soon as I get on format, the user server,

77
00:04:11.300 --> 00:04:13.800
 another attack be in the picture.

78
00:04:15.200 --> 00:04:18.400
 Where initially takako sends the

79
00:04:18.400 --> 00:04:21.800
 same social engineering tactics, you would send the

80
00:04:21.800 --> 00:04:24.300
 fix session ID, which he wants the

81
00:04:24.300 --> 00:04:25.100
 victim to use.

82
00:04:26.300 --> 00:04:29.200
 From there. The user will actually log

83
00:04:29.200 --> 00:04:32.200
 into the server. Without knowing the session ID

84
00:04:32.200 --> 00:04:36.200
 was already fixed. And that would be actually authenticated

85
00:04:35.400 --> 00:04:38.700
 and authorized by the server and

86
00:04:38.800 --> 00:04:40.000
 user will have the session.

87
00:04:41.100 --> 00:04:45.000
 And going forward, the victim can use ready-made

88
00:04:44.400 --> 00:04:45.900
 available session.

89
00:04:47.200 --> 00:04:48.900
 That's it for this video. Thank you.
