WEBVTT - This file was automatically generated by VIMEO

1
00:00:09.400 --> 00:00:12.800
 Welcome back. Let's take a look at the next Factor.

2
00:00:12.300 --> 00:00:15.500
 Called as session donation. Unlike

3
00:00:15.500 --> 00:00:18.200
 previous attack scenarios where the attacker was

4
00:00:18.200 --> 00:00:21.300
 trying to hijack the session itself. This is

5
00:00:21.400 --> 00:00:24.400
 more of a fishing based on tap. This attack is

6
00:00:24.400 --> 00:00:27.200
 something to be aware of because in this

7
00:00:27.300 --> 00:00:27.800
 attack,

8
00:00:28.500 --> 00:00:31.700
 The main purpose is to gain access to sensitive information

9
00:00:31.800 --> 00:00:32.300
 from the web.

10
00:00:33.500 --> 00:00:36.400
 As the name suggests, the keyword donation is

11
00:00:36.400 --> 00:00:39.900
 quite significant over you. Because the attacker is

12
00:00:39.900 --> 00:00:43.200
 trying to donate an existing profile such

13
00:00:42.200 --> 00:00:45.400
 that the victim believes its

14
00:00:45.400 --> 00:00:49.300
 own, and is going to fill out some information now,

15
00:00:49.300 --> 00:00:50.800
 let's let's take an example.

16
00:00:53.400 --> 00:00:56.600
 Taking a scenario where an attack of as created a

17
00:00:56.600 --> 00:00:59.300
 fake profile for Tom, Tom is

18
00:00:59.300 --> 00:01:02.300
 being the victim of you. So what he has done

19
00:01:02.300 --> 00:01:05.100
 is that he has restored and account or we

20
00:01:05.100 --> 00:01:08.500
 have of Tom, and as you can see

21
00:01:08.300 --> 00:01:11.900
 on the homepage that's a user profile, which

22
00:01:11.900 --> 00:01:14.600
 is asking for sensitive information such as

23
00:01:14.700 --> 00:01:15.400
 credit card.

24
00:01:16.700 --> 00:01:19.100
 So, main intent with attacker is to

25
00:01:19.100 --> 00:01:22.600
 create each account based on the victim.

26
00:01:23.600 --> 00:01:26.400
 Such that the victim believes that it

27
00:01:26.400 --> 00:01:29.500
 is his own account at he is willing to

28
00:01:29.500 --> 00:01:31.100
 send out some sense information.

29
00:01:32.100 --> 00:01:35.600
 Now, patient attack scenarios as we have seen in the previous

30
00:01:35.900 --> 00:01:38.900
 slides, that could be a combination of

31
00:01:38.900 --> 00:01:42.000
 attacks that could be used to gain access as

32
00:01:41.800 --> 00:01:44.200
 well. Maybe there's

33
00:01:44.200 --> 00:01:48.200
 a website which is actually available to cross-site scripting. So

34
00:01:47.200 --> 00:01:50.300
 the user will actually create

35
00:01:50.300 --> 00:01:53.600
 a profile and expecting the user to access it

36
00:01:53.600 --> 00:01:56.400
 through fishing mechanisms and

37
00:01:56.400 --> 00:01:59.400
 hoping that he can perform additional attacks in

38
00:01:59.400 --> 00:02:01.700
 order to gain access to the account sufficient.

39
00:02:02.400 --> 00:02:05.200
 Or exploiting process scripting or any

40
00:02:05.200 --> 00:02:08.400
 search scenarios for table, but just

41
00:02:08.400 --> 00:02:11.500
 focusing on the main intent of this attack. It is to ensure

42
00:02:11.500 --> 00:02:14.600
 that this account has been created by the attacker

43
00:02:14.600 --> 00:02:17.300
 and not by the victim and making

44
00:02:17.300 --> 00:02:20.300
 sure that the victim actually believes it is his own account.

45
00:02:21.400 --> 00:02:24.300
 So we do a scenario where the attacker was able

46
00:02:24.300 --> 00:02:27.800
 to fool the victim in order so

47
00:02:27.800 --> 00:02:30.300
 that you can click on the link and believing. It

48
00:02:30.300 --> 00:02:34.000
 is its own account and expecting the user to

49
00:02:33.300 --> 00:02:36.200
 update the profile. So this could be such a

50
00:02:36.200 --> 00:02:39.500
 scenario where the attacker just all go victim saying that hey

51
00:02:39.100 --> 00:02:43.000
 looks like a profile is incomplete. Please update

52
00:02:42.100 --> 00:02:45.800
 the profile in order to access some

53
00:02:45.800 --> 00:02:49.200
 deals. So it could be one such scenario, but

54
00:02:49.200 --> 00:02:51.100
 the main expectation is to

55
00:02:51.300 --> 00:02:55.100
 That though, victim accesses the account either

56
00:02:54.200 --> 00:02:57.500
 by loophole on the website. Such

57
00:02:57.500 --> 00:03:01.000
 that just by clicking on the URL, such in this generated

58
00:03:00.100 --> 00:03:04.300
 and the user is already logged in. So

59
00:03:03.400 --> 00:03:06.400
 since was his profile was

60
00:03:06.400 --> 00:03:09.200
 created by the attacker and is donating it to

61
00:03:09.200 --> 00:03:11.600
 the victim. Hence the name session donation.

62
00:03:13.400 --> 00:03:17.300
 Just to reiterate that occur is actually creating

63
00:03:16.400 --> 00:03:20.300
 a fake profile on the website such

64
00:03:20.300 --> 00:03:23.600
 that the user is actually being social engineer,

65
00:03:23.300 --> 00:03:26.600
 in order to access that particular profile.

66
00:03:26.300 --> 00:03:29.600
 And by accessing that the user might

67
00:03:29.600 --> 00:03:32.500
 want to believe that has its own account, and is

68
00:03:32.500 --> 00:03:36.400
 wanting fill out those sensitive divisions. And

69
00:03:36.500 --> 00:03:39.400
 once the user fills out the profile or ads

70
00:03:39.400 --> 00:03:42.400
 in sense of information, then it is up

71
00:03:42.400 --> 00:03:43.000
 to the user.

72
00:03:43.100 --> 00:03:46.900
 To just access the same account since he was the owner in

73
00:03:46.900 --> 00:03:49.600
 real sense. Now, you can access that

74
00:03:49.600 --> 00:03:53.000
 account and gain access to any sensitive information based

75
00:03:52.100 --> 00:03:55.800
 on whatever the website is incident intended

76
00:03:55.100 --> 00:03:56.600
 to do so.

77
00:03:57.800 --> 00:03:59.600
 There is for this video. Thank you.
