Abstract
The Android permission mechanism is designed to protect the privacy of Android users. An Android application must request permissions when it needs to access sensitive data at runtime. If users do not grant the application requested permissions, the application would not provide functionalities related to these permissions. However, some applications violate this purpose in that they request permissions at initialization. If the user does not grant the requested permissions, these applications would simply exit, refusing to provide any functionalities, including the ones that do not require sensitive data. This behavior of stubbornly requesting permissions damages the right of users in utilizing non-sensitive functionalities. To address this problem, we propose an approach to detect this kind of permission requests. First, we model the key features of stubborn permission requests. Then, we identify the stubborn permission requests by statically analyzing Android applications. We evaluate our approach with real-world market applications and the experimental result shows that our app roach can effectively detect stubborn permission requests in Android applications.
Published Version
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.