WEBVTT - This file was automatically generated by VIMEO

1
00:00:09.200 --> 00:00:13.000
 Read take a look at the idea of insecure logging when

2
00:00:12.100 --> 00:00:16.200
 we're actually working with applications on

3
00:00:15.200 --> 00:00:18.800
 Android devices were able to log things

4
00:00:18.800 --> 00:00:22.200
 into the log catalogs of our device. Know

5
00:00:21.200 --> 00:00:24.100
 it would be a lot of things to these laws. You have to

6
00:00:24.100 --> 00:00:27.400
 be careful of what sort of information to writing to them because we could

7
00:00:27.400 --> 00:00:31.200
 potentially expose information. At. Is sensitive. So

8
00:00:30.200 --> 00:00:33.500
 we're going to take a look at what this would usually

9
00:00:33.500 --> 00:00:36.400
 look like inside of an application and how we can stir to find

10
00:00:36.400 --> 00:00:40.800
 his vulnerabilities and determine if they exist. So for

11
00:00:39.800 --> 00:00:42.200
 someone to explain a little bit about

12
00:00:42.200 --> 00:00:46.000
 what does vulnerability is, and why it's important. So there

13
00:00:45.700 --> 00:00:48.800
 exists, a general logging area

14
00:00:48.800 --> 00:00:51.600
 on Android devices, that is typically referred

15
00:00:51.600 --> 00:00:56.500
 to as a log cat here.

16
00:00:57.100 --> 00:01:00.300
 So you could see shared that information is being

17
00:01:00.300 --> 00:01:03.500
 logged into this log and the sluggish shared by

18
00:01:03.500 --> 00:01:06.100
 which, we all the applications on the

19
00:01:06.100 --> 00:01:09.600
 actual device itself. And you can write things to the log fairly

20
00:01:09.600 --> 00:01:12.300
 easily. You think some built-in functions inside of

21
00:01:12.300 --> 00:01:15.700
 the Android, the Android development modules,

22
00:01:15.700 --> 00:01:18.500
 right? So you'll be able to, actually right information

23
00:01:18.500 --> 00:01:21.400
 to these debugging logs. Not only, can you write to

24
00:01:21.400 --> 00:01:24.600
 them, but you can also read them to see if a specific error has occurred.

25
00:01:24.600 --> 00:01:27.400
 The reason why we don't want to login, any sensitive

26
00:01:27.400 --> 00:01:30.200
 information to this is Sir to fold for one. As you can

27
00:01:30.200 --> 00:01:34.200
 see here. I can easily access the log cat likes, just

28
00:01:33.200 --> 00:01:36.800
 by having the device plugged into my computer or by

29
00:01:36.800 --> 00:01:40.100
 having the device running through an emulator on my computer, but

30
00:01:39.100 --> 00:01:42.200
 more. So that was important to

31
00:01:42.200 --> 00:01:45.200
 this is that somebody can actually create an app that can

32
00:01:45.200 --> 00:01:48.500
 read this log catalog. That means in terms, they can

33
00:01:48.500 --> 00:01:51.400
 read any messages that are logged here. So, if you,

34
00:01:51.400 --> 00:01:54.500
 for instance, are logging information about a user's password, or

35
00:01:54.500 --> 00:01:57.100
 something like that, if I have an application that sleep

36
00:01:57.100 --> 00:02:00.400
 Sniffing the log file on. This person's device. I'll be

37
00:02:00.400 --> 00:02:03.700
 able to see that information as well. Since you some context behind

38
00:02:03.700 --> 00:02:06.500
 dump. What does vulnerability really

39
00:02:06.500 --> 00:02:09.100
 is, and why it's important. So it's not really, just a matter of

40
00:02:09.100 --> 00:02:12.400
 like logging information that is sensitive such as I can epit or

41
00:02:12.400 --> 00:02:15.300
 something like that. That someone might see from, you know, we can

42
00:02:15.300 --> 00:02:18.700
 get the logs. It's also a matter of someone, you

43
00:02:18.700 --> 00:02:21.300
 know, what, third-party sort of like sniffing the log of

44
00:02:21.300 --> 00:02:25.200
 a random device to grab information about the user. So

45
00:02:24.200 --> 00:02:27.400
 they give you an example of this. Let's go ahead and

46
00:02:27.400 --> 00:02:29.700
 open up our Diva application.

47
00:02:30.700 --> 00:02:33.700
 I'm going to insecure logging and I'm

48
00:02:33.700 --> 00:02:36.300
 going to demonstrate to you. What exactly this could look like.

49
00:02:36.300 --> 00:02:39.600
 So you see here and here we want to enter credit card information

50
00:02:39.600 --> 00:02:42.400
 going to put in my credit card information and price.

51
00:02:42.400 --> 00:02:45.600
 When I do this, you're going

52
00:02:45.600 --> 00:02:48.100
 to see right here that there's an error message

53
00:02:48.100 --> 00:02:52.000
 that gets processed. It says error, while processing transaction

54
00:02:51.100 --> 00:02:54.200
 with credit card and then it prints out. The credit card

55
00:02:54.200 --> 00:02:57.500
 number to this is something that we want to avoid. This

56
00:02:57.500 --> 00:03:00.300
 would be an example of insecure logging. And the

57
00:03:00.300 --> 00:03:03.200
 reason being again is because if we have a third-party application, that's

58
00:03:03.200 --> 00:03:06.000
 a sniffing this log, if they see this error message,

59
00:03:06.600 --> 00:03:10.100
 it exposes the credit card information of the user. So

60
00:03:09.100 --> 00:03:12.800
 this is extremely bad because obviously, then

61
00:03:12.800 --> 00:03:15.300
 people can potentially have an information disclosure. They

62
00:03:15.300 --> 00:03:18.100
 could end up showing information to someone else. That

63
00:03:18.100 --> 00:03:21.500
 shouldn't your information will be able to compromise the message, right?

64
00:03:22.300 --> 00:03:25.700
 So we can take a look at the source code of this. That we've decompile

65
00:03:25.700 --> 00:03:28.100
 to get a bit of an idea of what this is

66
00:03:28.100 --> 00:03:31.100
 actually looking like in the code, just give you an idea

67
00:03:31.100 --> 00:03:33.800
 of what three things. You can look out for for this.

68
00:03:34.900 --> 00:03:38.000
 So we have this log activity. This this method

69
00:03:37.200 --> 00:03:40.300
 here log. He is what

70
00:03:40.300 --> 00:03:43.100
 happens when were trying to login error message. So there's like a

71
00:03:43.100 --> 00:03:46.200
 log. E4 error. I think log. D is debug and

72
00:03:46.200 --> 00:03:49.300
 there's probably a few other ones. They're very common. And as

73
00:03:49.300 --> 00:03:52.100
 you can see here, it gives the actual error message, and you

74
00:03:52.100 --> 00:03:55.300
 can see it actually writes in whatever is inside of the text box of the,

75
00:03:55.300 --> 00:03:58.200
 of the credit card filled. So you can see this

76
00:03:58.200 --> 00:04:01.200
 is what the actual log message looks like. So if we're looking

77
00:04:01.200 --> 00:04:04.600
 for these sort of instances, we can look for like a log. He

78
00:04:04.600 --> 00:04:07.300
 or log daddy, and he will show us where

79
00:04:07.300 --> 00:04:10.800
 the logs are being written to the actual to the

80
00:04:10.800 --> 00:04:13.200
 device lock itself. And then, from there, you can

81
00:04:13.200 --> 00:04:16.400
 try triggering. These are looking at what is actually being logged

82
00:04:16.400 --> 00:04:19.300
 to determine if that information is a sensitive data

83
00:04:19.300 --> 00:04:22.200
 or not. So common sense it, if they don't include things like

84
00:04:22.200 --> 00:04:25.400
 passwords and usernames that credit card

85
00:04:25.400 --> 00:04:30.200
 details, obviously personal details related to

86
00:04:30.200 --> 00:04:33.200
 that. The application would be a common

87
00:04:33.200 --> 00:04:34.700
 one on even be debate.

88
00:04:34.800 --> 00:04:37.500
 People named said, databases in general.

89
00:04:37.500 --> 00:04:40.100
 This sort of information leakage is the kind of stuff

90
00:04:40.100 --> 00:04:43.600
 that we want to make sure isn't happening in your application. So this

91
00:04:43.600 --> 00:04:46.400
 would be an example of insecure logging. So it

92
00:04:46.400 --> 00:04:49.500
 gives you an idea of what this vulnerability looks like and how to actually detect

93
00:04:49.500 --> 00:04:50.200
 it in an application.
