WEBVTT - This file was automatically generated by VIMEO

1
00:00:10.500 --> 00:00:13.400
 I thought it's a funnel kind of video. I could walk you through a

2
00:00:13.400 --> 00:00:16.400
 general process of trying to do some bug

3
00:00:16.400 --> 00:00:19.600
 hunting in Android to show. How I

4
00:00:19.600 --> 00:00:22.600
 would generally go about looking into an application. If

5
00:00:22.600 --> 00:00:25.300
 I were doing some research into one of the

6
00:00:25.300 --> 00:00:28.300
 very first thing is before I T compile an APK. I'm going

7
00:00:28.300 --> 00:00:31.300
 to install grocer and I'm going to try the following thinks I'm going

8
00:00:31.300 --> 00:00:34.100
 to run the attack surface command against the

9
00:00:34.100 --> 00:00:37.600
 application, to see what different attacks Services exist.

10
00:00:37.600 --> 00:00:40.400
 If I see that their activities that are exported and

11
00:00:40.400 --> 00:00:43.400
 that there scanners that are exported rather. I'm content

12
00:00:43.400 --> 00:00:46.500
 providers that are exported. I'm going to try to start every

13
00:00:46.500 --> 00:00:49.800
 activity to see what that gives me. If

14
00:00:49.800 --> 00:00:52.700
 that gives me something that looks to

15
00:00:52.700 --> 00:00:55.800
 be vulnerable or looks to be a problem. Then

16
00:00:55.800 --> 00:00:58.100
 I've already found some problems, right? And then I'm

17
00:00:58.100 --> 00:01:01.900
 going to run this injection command to see if any SQL

18
00:01:01.900 --> 00:01:04.600
 injections exist if they do exist, then we've

19
00:01:04.600 --> 00:01:05.700
 already found a problem, right?

20
00:01:05.800 --> 00:01:08.200
 These are some very good low-hanging fruits that

21
00:01:08.200 --> 00:01:12.700
 we can try to pick off when they're available, right from

22
00:01:11.700 --> 00:01:14.700
 this. We can also try decompiling, the

23
00:01:14.700 --> 00:01:17.400
 APK and there were few things that you should generally be

24
00:01:17.400 --> 00:01:21.400
 looking for, when you compile an APK. There's actually

25
00:01:21.400 --> 00:01:24.900
 one other thing that I'm going to adhere to the end so that we can

26
00:01:24.900 --> 00:01:27.900
 remember to discuss it, which would be load

27
00:01:27.900 --> 00:01:28.200
 URL.

28
00:01:29.700 --> 00:01:34.100
 But starting with these ones execute SQL,

29
00:01:33.100 --> 00:01:36.800
 write query Rock query. Least

30
00:01:36.800 --> 00:01:39.400
 three functions are always tipu

31
00:01:39.400 --> 00:01:42.300
 going to be used to execute SQL. We should always look

32
00:01:42.300 --> 00:01:45.400
 at them with great scrutiny to determine if they're using

33
00:01:45.400 --> 00:01:48.900
 parameterize queries, or if they're doing something unsafe. If

34
00:01:48.900 --> 00:01:51.400
 we see something unsafe that we can potentially reach with,

35
00:01:51.400 --> 00:01:54.300
 use your input. This gives us a place to potentially try

36
00:01:54.300 --> 00:01:57.600
 to attack. So these are really great to try

37
00:01:57.600 --> 00:02:00.400
 to search for in general most applications going

38
00:02:00.400 --> 00:02:03.200
 to have some form of database query. If you can find the

39
00:02:03.200 --> 00:02:06.500
 database queries, we could potentially do something here, which is

40
00:02:06.500 --> 00:02:09.800
 important to be able to determine an application. The

41
00:02:09.800 --> 00:02:12.800
 next thing is going to look for a log. Something. So

42
00:02:12.800 --> 00:02:15.500
 it's usually log. D log. If

43
00:02:15.500 --> 00:02:18.400
 you just type in the log. You'll be able to find anything that has

44
00:02:18.400 --> 00:02:21.100
 log being extended with some form of

45
00:02:21.100 --> 00:02:21.700
 method, right?

46
00:02:22.500 --> 00:02:25.500
 These are really important because they can tell us what sort of information is

47
00:02:25.500 --> 00:02:28.500
 being blocked by the application. This will be able to let

48
00:02:28.500 --> 00:02:31.600
 us like easily pick off any sort of ladybug, messages are

49
00:02:31.600 --> 00:02:34.400
 error messages that could expose something sensitive. We just

50
00:02:34.400 --> 00:02:37.200
 need to determine how to get down that branch of code, and then we'll

51
00:02:37.200 --> 00:02:41.200
 be able to expose those log values easily. The next

52
00:02:41.200 --> 00:02:44.000
 thing is going to be the search for password in general. Most people are in

53
00:02:44.200 --> 00:02:47.100
 a hard card passwords, but just in case of the password, could

54
00:02:47.100 --> 00:02:50.300
 be a good thing to search. For if you see password equals something in, plain text

55
00:02:50.300 --> 00:02:53.400
 to then you've obviously found some sort of problems. So that's always

56
00:02:53.400 --> 00:02:56.500
 a good one to search for shared preferences is

57
00:02:56.500 --> 00:02:59.400
 a really good thing to look for. This will be any, the shirt preference is

58
00:02:59.400 --> 00:03:02.300
 files. If you're ready to start preferences, odds are that dude is

59
00:03:02.300 --> 00:03:05.500
 not going to be secure. If you can see, what kind of data is being written and

60
00:03:05.500 --> 00:03:08.500
 we see that it's something that should be treated with security. Check

61
00:03:08.500 --> 00:03:10.300
 references is going to be a good week, too.

62
00:03:12.200 --> 00:03:15.400
 Democratic file is being created in the temp file

63
00:03:15.400 --> 00:03:18.300
 that again, has some sort of data and it that's supposed to

64
00:03:18.300 --> 00:03:21.400
 be secure. Then we could potentially expose that,

65
00:03:21.400 --> 00:03:24.000
 right? So, this is a good thing to look for, as well. To see,

66
00:03:24.200 --> 00:03:27.100
 what kind of data gets written to Temp files. Exact is a

67
00:03:27.100 --> 00:03:31.100
 general sort of command that's used by Java to execute command

68
00:03:30.100 --> 00:03:33.300
 line. Type argument is a few different

69
00:03:33.300 --> 00:03:36.500
 ones that exist somebody specifically for Android

70
00:03:36.500 --> 00:03:39.500
 as well. If you ever see command line

71
00:03:39.500 --> 00:03:42.100
 being run with a user input, you might be able to

72
00:03:42.100 --> 00:03:45.300
 hit command injection, which is a very severe pain or

73
00:03:45.300 --> 00:03:48.200
 ability. So, I typically look for these and look for

74
00:03:48.200 --> 00:03:51.300
 your input is being allowed in them. If that

75
00:03:51.300 --> 00:03:54.300
 ever happens. We want to try to test that to see if we can do some

76
00:03:54.300 --> 00:03:57.100
 sort of command injection on it right now, in a course to

77
00:03:57.100 --> 00:04:00.400
 load URL, because we've learned, we can load URL. So we

78
00:04:00.400 --> 00:04:03.400
 can load files through the load URL function. So am

79
00:04:03.400 --> 00:04:06.300
 I ever get the opportunity to get data into load

80
00:04:06.300 --> 00:04:09.500
 URL, we might be able to load a specific file utilizing that.

81
00:04:09.500 --> 00:04:12.000
 So this is something to always look out for us.

82
00:04:12.200 --> 00:04:15.200
 So in general or do these videos, you should have

83
00:04:15.200 --> 00:04:18.500
 a pretty good understanding of how to hunt for vulnerabilities in Android

84
00:04:18.500 --> 00:04:21.600
 and how to be able to expose those vulnerabilities through

85
00:04:21.600 --> 00:04:24.400
 decompiling as well as utilizing tools. Like

86
00:04:24.400 --> 00:04:27.400
 grocer up a general. This should give you a little bit

87
00:04:27.400 --> 00:04:30.100
 of an overview towards the general flow of what we

88
00:04:30.100 --> 00:04:33.200
 typically look for in vulnerabilities and like how we

89
00:04:33.200 --> 00:04:36.100
 typically go about looking for the how someone like me would go

90
00:04:36.100 --> 00:04:39.500
 about looking for a vulnerability if I'm searching for what? So

91
00:04:39.500 --> 00:04:42.200
 this should give you some good information to

92
00:04:42.200 --> 00:04:45.100
 be able to get up there and start bug hunting, and Android. Whether it

93
00:04:45.100 --> 00:04:48.500
 be your own applications or looking for bug bounties

94
00:04:48.500 --> 00:04:51.400
 or testing other people's applications. This will

95
00:04:51.400 --> 00:04:54.400
 give you a good solid foundations to be able to try out some

96
00:04:54.400 --> 00:04:57.400
 vulnerability. Send learn all sorts of new stuff with

97
00:04:57.400 --> 00:04:59.200
 this using a sort of like a good foundation.
