Android OEM's applications (in)security and backdoors ... - QuarksLAB

More documents

Recommendations

Info

Android introduction Android security model Methodology Toward a backdoor without permission Post-exploitation The permission system Application restrictions Least privilege security Permission to protect against dangerous actions: SD card write access, INTERNET access, sending SMS, ... By default, an application doesn’t have any permission You need to ask for them explicitly in AndroidManifest.xml Asked permissions are shown to the user at installation Boolean choice A permission can protect: Functions: AccountManager.getAccounts() (GET_ACCOUNTS) Intents: android.intent.action.CALL (CALL_PHONE) Components: content://contacts (READ_CONTACTS, ...) A permission is given to an UID and not to a packagename Permission model is applied on native code too All permissions of each application with the same sharedUserId are combined
Android introduction Android security model Methodology Toward a backdoor without permission Post-exploitation The permission system Application restrictions Consequences of the permission model Components can be protected The user ”knows” what the application can do when it is installed, thus the associated risks Limit the impact in case of vulnerable application
Page 1 and 2: Android OEM’s applications (in)se
Page 3 and 4: Android introduction Android securi
Page 27: Android introduction Android securi
Page 78 and 79:
Android introduction Android securi
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112:
contact@quarkslab.com I @quarkslab.
show all

Android OEM's applications (in)security and backdoors ... - QuarksLAB

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?