WEBVTT - This file was automatically generated by VIMEO

1
00:00:05.600 --> 00:00:08.600
 One of the first things that we would typically do

2
00:00:08.600 --> 00:00:11.200
 with drozer, is utilize it to find an

3
00:00:11.200 --> 00:00:15.200
 attack surface of the application were looking to attack. So the

4
00:00:15.200 --> 00:00:18.200
 very first thing that you can do to your ID you could do. You could

5
00:00:18.200 --> 00:00:20.900
 run up that package. List.

6
00:00:21.700 --> 00:00:24.400
 With this will do as well list off. Like I said, all of the applications

7
00:00:24.400 --> 00:00:27.600
 that are currently installed on the device. And as

8
00:00:27.600 --> 00:00:30.600
 you recall, we were using the diva app, which has this

9
00:00:30.600 --> 00:00:33.600
 package name associated with it. This package

10
00:00:33.600 --> 00:00:36.200
 name is what we're going to be using in Crozer to tell

11
00:00:36.200 --> 00:00:39.900
 it what application tax should be skin. So they're

12
00:00:39.900 --> 00:00:43.200
 a few different like information-gathering type

13
00:00:42.200 --> 00:00:46.200
 of commands that we can run through drozer, to

14
00:00:45.200 --> 00:00:48.500
 be able to get a general information about the application that

15
00:00:48.500 --> 00:00:49.600
 we're looking to attack.

16
00:00:50.900 --> 00:00:53.900
 The first going to be, run up that

17
00:00:53.900 --> 00:00:54.700
 package.

18
00:00:55.800 --> 00:00:58.800
 Dot info and Who provided -

19
00:00:58.800 --> 00:01:01.100
 a fruit argument to me? Give it the name of

20
00:01:01.100 --> 00:01:02.700
 the application who wish to scan?

21
00:01:04.100 --> 00:01:07.600
 What is it going to do with its going to give you a general overview of

22
00:01:07.600 --> 00:01:10.200
 details about the application with that means

23
00:01:10.200 --> 00:01:13.400
 it's going to tell you where the data directory is. For instance, somewhere.

24
00:01:13.400 --> 00:01:16.700
 The APK path is what you ideas

25
00:01:16.700 --> 00:01:19.000
 used with it. What version the application is the

26
00:01:19.300 --> 00:01:22.600
 name of it, the process name, you know, anything that's really relevant or

27
00:01:22.600 --> 00:01:25.400
 interesting on what permissions that uses for instance, as

28
00:01:25.400 --> 00:01:28.300
 well. So use instead of a high-level understanding of

29
00:01:28.300 --> 00:01:31.000
 information about the application, it something else like to

30
00:01:31.200 --> 00:01:35.000
 give us something similar would be up that package. Manifest.

31
00:01:36.300 --> 00:01:39.300
 This when you don't have to provide an argument, you just put in the name

32
00:01:39.300 --> 00:01:42.900
 of the application. You don't have to put the - A and this

33
00:01:42.900 --> 00:01:45.100
 will give you the whole manifest file of the

34
00:01:45.100 --> 00:01:48.700
 application itself. So if you remember, we we decompiled the application.

35
00:01:48.700 --> 00:01:51.300
 We could reach this through this manifests, the

36
00:01:51.300 --> 00:01:54.600
 inside of the resources to this is the same information is

37
00:01:54.600 --> 00:01:57.200
 what we're getting here. The reason

38
00:01:57.200 --> 00:02:00.600
 why we want to see this because you can show us information about like you

39
00:02:00.600 --> 00:02:04.000
 man-cub from missions, are being used versions of

40
00:02:03.300 --> 00:02:07.000
 the of the SEK. It's targeting. And

41
00:02:06.200 --> 00:02:09.300
 in general Aiken, tells a lot of very good piece of

42
00:02:09.300 --> 00:02:12.700
 information such as intense that may exist activities. That

43
00:02:12.700 --> 00:02:15.300
 may exist providers, that

44
00:02:15.300 --> 00:02:18.600
 may exist. So we get a whole bunch of information about the providers

45
00:02:18.600 --> 00:02:21.300
 and activities and such. So if

46
00:02:21.300 --> 00:02:24.800
 you want to take this a little bit further service to

47
00:02:24.800 --> 00:02:27.800
 get, I do, I'm more like generalized format

48
00:02:27.800 --> 00:02:30.200
 of the more like

49
00:02:30.200 --> 00:02:33.100
 a summery summary of the Manifest file to tell us all

50
00:02:33.100 --> 00:02:36.300
 the information with the things that we could possibly talk to me application.

51
00:02:36.400 --> 00:02:38.400
 So I got to run them.

52
00:02:39.400 --> 00:02:42.800
 Let's see us up that package. Attack surface.

53
00:02:44.600 --> 00:02:46.700
 Open the name the application.

54
00:02:49.400 --> 00:02:52.200
 But this will do as it was skinny application to tell you information

55
00:02:52.200 --> 00:02:56.100
 about the attack surface. So it tells us about activities broadcast receivers

56
00:02:55.100 --> 00:02:58.500
 content providers in services. And also

57
00:02:58.500 --> 00:03:01.800
 tells us that the application is debuggable or not, which of

58
00:03:01.800 --> 00:03:04.300
 these are things that we might be able to attack of this

59
00:03:04.300 --> 00:03:07.600
 one's got activities and content providers. These are

60
00:03:07.600 --> 00:03:10.400
 able to be used for activities, typically

61
00:03:10.400 --> 00:03:14.000
 could show his potential Access Control violations. Rest

62
00:03:13.300 --> 00:03:16.900
 content providers could potentially show us some instances

63
00:03:16.900 --> 00:03:19.400
 where queries might be able to be used to

64
00:03:19.400 --> 00:03:22.800
 undo SQL injection and that sort of thing. So this

65
00:03:22.800 --> 00:03:25.300
 helps to expose the general attack surface of her

66
00:03:25.300 --> 00:03:28.200
 application and helps us gather a bit more information about the

67
00:03:28.200 --> 00:03:31.100
 application itself. And then from here, we can take a look at some

68
00:03:31.100 --> 00:03:34.000
 of the different types of attacks that we can do inside of dresser.
