Android permissions demystified

By Adrienne Porter Felt, Erika Chin, Steve Hanna, Dawn Song, David A. Wagner. Conference on Computer and Communications Security, 2011

1,572 citations recorded by the source corpus.

Subfields: Information Systems, Software, Signal Processing

View Paper: https://www.semanticscholar.org/paper/bd736ada1822b69e13d5a5aa68acc84cb9c5fb36

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Information Systems

In Software

In Signal Processing

Citations in the corpus

Mobile-sandbox: having a deeper look into android applications (2013, methodology): “[9] which we translated from Java to smali.”
A Machine-learning Approach for Classifying and Categorizing Android Sources and Sinks (2014, methodology): “These methods can be identified using a permission map which can be created either statically [22], [23] or dynamically [24].”
DroidMat: Android Malware Detection through Manifest and API Calls Tracing (2012, background): “Particularly, we focus on those permission-protected APIs from the permission map [16].”
DREBIN: Effective and Explainable Detection of Android Malware in Your Pocket (2014, methodology): “Similarly, Stowaway [15] analyzes API calls to detect overprivileged applications and RiskRanker [21] statically identifies applications with different security risks.”
Structural detection of android malware using embedded call graphs (2013, background): “[14] go one step further by correlating requested permissions with statically observable API calls to detect overprivileged applications.”
MaMaDroid: Detecting Android Malware by Building Markov Chains of Behavioral Models (2016, background): “[21], who analyze API calls to identify over-privileged apps, while Kirin [20] is a system that examines permissions requested by apps to perform a lightweight certification, using a set of security rules that indicate whether or not the security configuration bundled with the app is safe.”
A Conundrum of Permissions: Installing Applications on an Android Smartphone (2012, background): “, in their Android Permissions Demystified work, attempt to further explain permissions to developers [5].”
Automated concolic testing of smartphone apps (2012, background): “We also describe our implementation of the approach for Android, the most popular smartphone app platform, and the results of an evaluation that demonstrates its e.ectiveness on .ve Android apps.”
The Art, Science, and Engineering of Fuzzing: A Survey (2018, methodology): “ing dynamic symbolic execution [93], [236], grammar-based test case generation [91], [109], [223], permission testing [27], [83], behavioral testing [126], [182], [234], complexity test-”
Security Analysis of Emerging Smart Home Applications (2016, methodology): “Prior work has used binary instrumentation coupled with automated testing to observe the runtime behavior of apps to infer the set of operations associated with a particular capability [13].”
An empirical study of cryptographic misuse in android applications (2013, background): “Furthermore, the Android permission system has been at the core of many scientific publications [14, 16, 24].”
Privacy as part of the app decision-making process (2013, background): “, in their Android Permissions Demystified paper, attempt to further explain permissions to developers [6].”
Spearphone: A Speech Privacy Exploit via Accelerometer-Sensed Reverberations from Smartphone Loudspeakers (2019, background): “Moreover, many apps are designed to be overprivileged by developers [28].”
SoK: Privacy on Mobile Devices – It’s Complicated (2016, methodology): “Various studies have approximated that a significant amount of Android applications (one-third of 940 [90], 44% of 10,000 [150]), in fact, request permissions that they do not use.”
Towards Taming Privilege-Escalation Attacks on Android (2012, neutral): “Note that in contrast to [15] [19] we perform our evaluation manually at runtime 3 , and hence, 50 applications are already sufficient for our purposes.”
Brave new world: privacy risks for mobile users (2014, background): “In addition, many apps do not follow the rule of least privilege when requesting permissions [19].”
Checking app behavior against app descriptions (2014, methodology): “, who identified and used the mapping between permissions and Android methods [7]; we considered a sensitive API to be used by the app if and only if it is declared in the binary and if its corresponding permission is requested in the manifest file.”
Edge Computing Security: State of the Art and Challenges (2019, background): “[155] found that about one-third of the Android apps have the overprivileged problem.”