2011 IEEE 13th International Conference on Communication Technology 2011
DOI: 10.1109/icct.2011.6157963
|View full text |Cite
|
Sign up to set email alerts
|

A privilege escalation vulnerability checking system for android applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
14
0

Year Published

2014
2014
2018
2018

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 12 publications
(14 citation statements)
references
References 6 publications
0
14
0
Order By: Relevance
“…Table tells us that there are 679 applications that do not call any sensitive functions listed in Table from exported interfaces, which cannot endanger our mobiles but reported as vulnerable in in these 1929 applications with exported interfaces. The other 1250 applications have public exported interfaces and invoke sensitive functions from these interfaces, which may endanger our phones.…”
Section: Evaluation and Resultsmentioning
confidence: 99%
See 2 more Smart Citations
“…Table tells us that there are 679 applications that do not call any sensitive functions listed in Table from exported interfaces, which cannot endanger our mobiles but reported as vulnerable in in these 1929 applications with exported interfaces. The other 1250 applications have public exported interfaces and invoke sensitive functions from these interfaces, which may endanger our phones.…”
Section: Evaluation and Resultsmentioning
confidence: 99%
“…A similar system has been presented in , however, without code‐level detecting, the system only checks the AndroidManifest file that provides indispensable information about the application, which leads to a higher false positive ratio. Our contributions in this paper are as follows: (1) we have designed and implemented a novel code‐level tool, PaddyFrog, to detect the confused deputy vulnerability in Android applications.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…A vulnerable and exported component can be visited by the other apps in the same device, which can lead to many types of vulnerabilities, e.g., capability leak [1,2], content provider leakage [3,4], privilege escalation [5,6], confused deputy [7], component hijacking [8,9], intent spoofing [10], etc. But these vulnerabilities can only be exploited locally (the vulnerable app and the malicious app must run in a same device).…”
Section: Related Workmentioning
confidence: 99%
“…To understand the universality of port-opening Android apps, we made a statistical analysis to the apps downloaded from Google Play 4 and Wandoujia (a famous Android app store in China 5 ). The download time of the apps is from July 2016 to October 2016.…”
Section: Universality Of Port-opening Android Appsmentioning
confidence: 99%