On Demystifying the Android Application Framework: Re-Visiting Android...
summary
A static-analysis pipeline builds a runtime model of Android’s framework, enumerates binder entry points, and models handler/channel/state-machine concurrency to produce API→permission maps; the tool Explorer reports far fewer false positives than PScout, connects SDK calls to valid framework entry points, and shows SDK mappings collapse many spurious multi-permission outliers. Manual labeling yields a taxonomy where 70% field updates dominate and unexpectedly finds >50 runtime exceptions across versions. Analysis quantifies permission locality (≈20% of permissions checked in multiple classes) and proposes single-enforcement points.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:21Motivation
- 2:20Contributions
- 3:36Analysis Ingredients
- 5:40Static Runtime Model (2)
- 7:05Static Runtime Model - Handler
- 8:57Protected Resources (13)
- 10:07Taxonomy of Protected Resource Types
- 13:36More Effort = Better Results?
- 14:59Framework API Mapping
- 16:35Android Permission Mappings - SDK
- 16:53SDK Mapping (1)
- 21:52Low Permission Locality
- 24:17Conclusion
related talks
50mAndrobugs Framework: An Android Application Security Vilnerability Scanner
37mHey, You, Get off My Private Data: Do Apps Respect Your Privacy as They Claim?
45mPerforming Due Diligence as Android Developers
29mSecuring Android Applications - The not so se…
54mUnwrapping the Truth: Analysis of Mobile Application Wrapping Solutions
53mAndroid: He protec, but he also attac
34mSecuring Android: Tackling Advanced Threats and Enhancing App Security
38mAdvanced Techniques for Protecting Android Apps