2013
DOI: 10.1007/978-3-319-01604-7_40
|View full text |Cite
|
Sign up to set email alerts
|

Android Security, Pitfalls and Lessons Learned

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0
1

Year Published

2013
2013
2017
2017

Publication Types

Select...
4
2
2

Relationship

2
6

Authors

Journals

citations
Cited by 13 publications
(7 citation statements)
references
References 3 publications
0
6
0
1
Order By: Relevance
“…Unfortunately, real attacks show that DEP and PXN can be fully bypassed by code reuse attack, such as ROP, which leverages existing native code in memory as shellcode payload instead of injecting custom malicious instructions [7,8]. ASLR is supported since Android kernel version 2.6.35 [9]. It allows the kernel to randomize the stack address, heap address, the location of shared libraries and other key memory areas.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Unfortunately, real attacks show that DEP and PXN can be fully bypassed by code reuse attack, such as ROP, which leverages existing native code in memory as shellcode payload instead of injecting custom malicious instructions [7,8]. ASLR is supported since Android kernel version 2.6.35 [9]. It allows the kernel to randomize the stack address, heap address, the location of shared libraries and other key memory areas.…”
Section: Related Workmentioning
confidence: 99%
“…However, SELinux can be broken through by corrupting the security identifier and security context of process credentials, and real attacks show that mitigation technology can be bypass by other exploit technology, e.g. Return-Oriented Programming (ROP) [4][5][6][7][8][9]. Some researchers suggested static detection methods to recognize privilege escalation attack [10,11], but they all rely on the source code and predefined features.…”
Section: Introductionmentioning
confidence: 99%
“…Even Apple's iOS and Google's Android 1 mobile operating systems have implemented ASLR [20], though Android's low entropy has been found to be ineffective against all but the simplest of attacks [21]. With so many operating systems and therefore such a large portion of users relying on ASLR, it is important to investigate how well such implementations secure their environments.…”
Section: Related Workmentioning
confidence: 99%
“…Liebergeld and Lange [17] discuss the risks that users run if they root their Android devices while Rogers [22] provides a similar discussion of some of the dangers of jailbreaking an iOS device. Since neither Android nor iOS are designed to have administration accounts running, despite being both based on Unix-related kernels (Linux and XNU, respectively) once the systems have been hacked to expose these administrator-level accounts, they are more likely to be vulnerable to external hacking.…”
Section: Direct Security Risks Of Rooting/jailbreakingmentioning
confidence: 99%