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 A huge surface attack A huge surface attack A large number of applications Only two folders examined, but a consequent attack surface 216 APK in /system/app To compare: 91 APK for the Nexus 4
Android introduction Android security model Methodology Toward a backdoor without permission Post-exploitation Vulnerability research Automation Constraints Many application, need automation to find interesting applications Then audit by hand (reverse engineering) Exploitation of vulnerabilities with a little amount or no permission at all Creation of some scripts: ASA Based on Androguard (great framework) ASAManifest: Analyzes the manifest of an application and tells which components are exported and under what conditions ASADatabase: Analyzes a large amount of applications like ASAManifest does and checks for sensitive API usage. The results are stored in MongoDB database. ASADiff (ongoing): Diff between two versions of a system, by example to detect vulnerability patching.
Page 1 and 2: Android OEM’s applications (in)se
Page 3 and 4: Android introduction Android securi
Page 31: Android introduction Android securi
Page 82 and 83:
Android introduction Android securi
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?