TL;DR
RAICC is a static analysis tool that uncovers atypical inter-component communication methods in Android apps, improving detection of vulnerabilities and privacy leaks beyond traditional framework-based approaches.
Contribution
RAICC introduces a novel static approach to model atypical ICC links, enhancing existing analysis tools for better vulnerability and leak detection.
Findings
RAICC improves precision and recall of leak detection.
Atypical ICC methods are widely used in Android apps.
RAICC increases ICC link detection by 61.6% in malicious apps.
Abstract
Inter-Component Communication (ICC) is a key mechanism in Android. It enables developers to compose rich functionalities and explore reuse within and across apps. Unfortunately, as reported by a large body of literature, ICC is rather "complex and largely unconstrained", leaving room to a lack of precision in apps modeling. To address the challenge of tracking ICCs within apps, state of the art static approaches such as Epicc, IccTA and Amandroid have focused on the documented framework ICC methods (e.g., startActivity) to build their approaches. In this work we show that ICC models inferred in these state of the art tools may actually be incomplete: the framework provides other atypical ways of performing ICCs. To address this limitation in the state of the art, we propose RAICC a static approach for modeling new ICC links and thus boosting previous analysis tasks such as ICC…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Code & Models
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
