WEBVTT - This file was automatically generated by VIMEO

1
00:00:04.800 --> 00:00:07.400
 What are the things that

2
00:00:07.400 --> 00:00:10.300
 would be very helpful in terms of analyzing in

3
00:00:10.300 --> 00:00:13.800
 for the applications, for vulnerabilities, has the ability to decompile the

4
00:00:13.800 --> 00:00:18.300
 application back into its source code Java languages

5
00:00:17.300 --> 00:00:20.300
 that are similar to Java that compiled into

6
00:00:20.300 --> 00:00:23.700
 a bike coat that is running against virtual machine.

7
00:00:23.700 --> 00:00:26.400
 It's possible for us to reverse the compilation

8
00:00:26.400 --> 00:00:29.900
 process to turn the bike could back into something

9
00:00:29.900 --> 00:00:32.500
 that resembles the original source code of the

10
00:00:32.500 --> 00:00:36.000
 matching won't always be perfect. You will do some information

11
00:00:35.600 --> 00:00:38.300
 typically from it. However, most of

12
00:00:38.300 --> 00:00:41.200
 the important pieces are going to still be there and since those

13
00:00:41.200 --> 00:00:44.500
 pieces will be, there will be able to not only understand what

14
00:00:44.500 --> 00:00:47.500
 the application is doing but actually be able to see the source code

15
00:00:47.500 --> 00:00:50.000
 and be able to pick out specific, vulnerable aspects that

16
00:00:50.200 --> 00:00:53.100
 we want to be able to work with Sol. In this video May

17
00:00:53.100 --> 00:00:56.500
 demonstrate how we can reverse reverse engineer

18
00:00:56.500 --> 00:00:59.500
 essentially what he compiled an application. So there's

19
00:00:59.500 --> 00:01:02.200
 a lot of different ways that people would typically used to do this

20
00:01:02.200 --> 00:01:04.700
 their chores, like apt to land.

21
00:01:04.700 --> 00:01:07.400
 Igd that will allow us to

22
00:01:07.400 --> 00:01:11.000
 decompile the application

23
00:01:10.200 --> 00:01:13.300
 and then reverse it back into Java code.

24
00:01:13.300 --> 00:01:17.100
 I actually used one called jednej a

25
00:01:17.100 --> 00:01:20.000
 DX and I cannot put links to

26
00:01:20.300 --> 00:01:23.400
 these inside of a resources section, but I'm inside

27
00:01:23.400 --> 00:01:26.400
 of here. There is essentially in the bin. There's

28
00:01:26.400 --> 00:01:29.300
 a gooey that we can launch watch this for

29
00:01:29.300 --> 00:01:32.200
 able to actually decompile any APK that

30
00:01:32.200 --> 00:01:35.300
 we may have on our computer. So I had to come into our

31
00:01:35.300 --> 00:01:38.700
 directory here and I'm going to go grab the application that

32
00:01:38.700 --> 00:01:41.500
 we installed and I run this through the decompiler.

33
00:01:42.500 --> 00:01:45.400
 And what you see here is that we'll get a set of source code

34
00:01:45.400 --> 00:01:48.100
 and the set of resources that are used inside of this

35
00:01:48.100 --> 00:01:48.300
 application.

36
00:01:49.700 --> 00:01:52.100
 When you're first looking at an application, is a lot

37
00:01:52.100 --> 00:01:55.500
 of different information that's valuable to us. The Manifest file

38
00:01:55.500 --> 00:01:58.600
 is one that's going to be extremely useful to tell

39
00:01:58.600 --> 00:02:01.400
 you a lot of different things. Such as the permissions that are used by

40
00:02:01.400 --> 00:02:04.400
 the application. They will tell you what activities exist, inside

41
00:02:04.400 --> 00:02:07.600
 the application. They will tell you about intense. It will

42
00:02:07.600 --> 00:02:10.700
 tell you about things, like content providers

43
00:02:10.700 --> 00:02:13.900
 and such if they exist and it will tell you what versions

44
00:02:13.900 --> 00:02:16.100
 We Target, it will give

45
00:02:16.100 --> 00:02:19.100
 you a whole plethora of high-level information that will allow you

46
00:02:19.100 --> 00:02:23.100
 to better understand the attack surface that you're working with. So

47
00:02:22.100 --> 00:02:25.500
 this is one file. That would be very useful for

48
00:02:25.500 --> 00:02:28.500
 us to be able to look at resources are

49
00:02:28.500 --> 00:02:31.400
 going to be a lot of like the the graphical interface is in

50
00:02:31.400 --> 00:02:34.500
 such that you going to be working with a lot of this really isn't

51
00:02:34.500 --> 00:02:37.500
 particularly useful. I don't think most of

52
00:02:37.500 --> 00:02:40.300
 the time. This is just a white guy. You don't search for

53
00:02:40.300 --> 00:02:43.800
 your information that comes from this process. The medit

54
00:02:43.800 --> 00:02:47.200
 in full, tell you different information through some certificate details

55
00:02:46.200 --> 00:02:48.800
 that are sometimes.

56
00:02:49.700 --> 00:02:52.300
 Helpful, I'm at was a manifest file, which

57
00:02:52.300 --> 00:02:56.400
 I could tell you a little bit of valuable information. Potentially give

58
00:02:55.400 --> 00:02:58.100
 you a bit of a layout of all the things

59
00:02:58.100 --> 00:03:02.000
 that exist inside of like the red folder and it

60
00:03:01.200 --> 00:03:04.200
 will allow you to get a bit of

61
00:03:04.200 --> 00:03:07.700
 an understanding behind like the contents sofa of the

62
00:03:07.700 --> 00:03:15.100
 Manifest. For instance, Library, Syracuse,

63
00:03:14.100 --> 00:03:17.300
 instead of the application fees are typically written

64
00:03:17.300 --> 00:03:20.900
 in C or C plus plus and compiled. These can't

65
00:03:20.900 --> 00:03:23.100
 be a decompiled what we can do

66
00:03:23.100 --> 00:03:26.100
 with these. We can analyze like strings that makes sense. I thought

67
00:03:26.100 --> 00:03:29.600
 we might be able to break it down into something that

68
00:03:29.600 --> 00:03:32.400
 might be able to tell us some information about the

69
00:03:32.400 --> 00:03:35.500
 shared Library are shared object. But I want to

70
00:03:35.500 --> 00:03:38.900
 time these are things that we won't be able to necessarily taken

71
00:03:38.900 --> 00:03:41.600
 too, too deeply. We will see you in a few examples. We

72
00:03:41.600 --> 00:03:44.600
 actually can go through these and gain some form of relevant

73
00:03:44.600 --> 00:03:44.900
 information.

74
00:03:46.300 --> 00:03:49.200
 And finally, we have her actual source code files which are

75
00:03:49.200 --> 00:03:52.200
 the actual source of the application itself. If you take

76
00:03:52.200 --> 00:03:55.200
 a look at these, you'll be able to see you like each of the different pieces that

77
00:03:55.200 --> 00:03:58.200
 goes into building the actual application itself. So you

78
00:03:58.200 --> 00:04:01.400
 can you pull up any of the code that actually exists and you'll

79
00:04:01.400 --> 00:04:04.900
 be able to see exactly what code is being used. You can

80
00:04:04.900 --> 00:04:07.600
 do this sort of thing with all. I would

81
00:04:07.600 --> 00:04:10.000
 say, basically any Android application, you should be able

82
00:04:10.100 --> 00:04:14.100
 to get service code unless it's like heavily encrypted or

83
00:04:13.100 --> 00:04:16.600
 obscured in some way. This will

84
00:04:16.600 --> 00:04:17.700
 typically be possible.

85
00:04:18.600 --> 00:04:21.400
 It's a few other things that are useful for this. We can

86
00:04:21.400 --> 00:04:24.500
 search this for specific keywords. So Fritz if we

87
00:04:24.500 --> 00:04:27.300
 find like an error message or something like that that we want

88
00:04:27.300 --> 00:04:30.100
 to look up. We can try looking it up. You can try

89
00:04:30.100 --> 00:04:33.200
 looking up, things like password. See you want to check out like what

90
00:04:33.200 --> 00:04:36.500
 you asked me to search, you can search classes. You can search methods Fields

91
00:04:36.500 --> 00:04:39.400
 a code for instance and you can see here.

92
00:04:39.400 --> 00:04:42.200
 We can serve like pick out pieces of information that might be of interest

93
00:04:42.200 --> 00:04:45.100
 to us. So here's an example here. Where

94
00:04:45.100 --> 00:04:48.100
 were in sitting at this equal, a user username and a

95
00:04:48.100 --> 00:04:51.400
 password. It seems so hot. This, for instance, would be some

96
00:04:51.400 --> 00:04:55.200
 information that might be able to gather from decompiling the application. So

97
00:04:54.200 --> 00:04:57.200
 this is your idea of how we can.

98
00:04:57.200 --> 00:05:00.200
 I see decompile Android applications. And from here. We

99
00:05:00.200 --> 00:05:03.500
 have all the tools that were going to need to how to be

100
00:05:03.500 --> 00:05:06.500
 able to analyze different applications to

101
00:05:06.500 --> 00:05:09.100
 be able to look at common Android vulnerabilities. So that's what

102
00:05:09.100 --> 00:05:10.100
 we will take a look at next.
