2022
DOI: 10.1109/tdsc.2021.3075817
|View full text |Cite
|
Sign up to set email alerts
|

LibCapsule: Complete Confinement of Third-Party Libraries in Android Applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
7
0

Year Published

2022
2022
2024
2024

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 8 publications
(7 citation statements)
references
References 34 publications
0
7
0
Order By: Relevance
“…e second approach is to design a more granular permission mechanism that restricts the interaction between TPLs and resources. For example, FLEXDROID [16], Zhan et al [17], LIB CAPSULE [18], and others enable the Android system to manage TPLs permissions directly by implementing librarylevel access control mechanisms.…”
Section: Introductionmentioning
confidence: 99%
“…e second approach is to design a more granular permission mechanism that restricts the interaction between TPLs and resources. For example, FLEXDROID [16], Zhan et al [17], LIB CAPSULE [18], and others enable the Android system to manage TPLs permissions directly by implementing librarylevel access control mechanisms.…”
Section: Introductionmentioning
confidence: 99%
“…Although TPLs bring functionality conveniences, TPLs also import data leakage. According to Android permission mechanism, TPLs share the same privileges with host apps [19]- [21]. TPLs may abuse permissions to access users' personally identifiable information without users' consent [22], [23], which results in personal information leakage [8]- [18], [53].…”
Section: A Android Third-party Librariesmentioning
confidence: 99%
“…ATPChecker finds the variable (srcv) in srcstmt that corresponds to DOI vt (line 17). If srcv is a variable, ATPChecker continues backward analysis, starts with srcstmt in srcm and focuses analysis on variable srcv (line [18][19]; if srcv is a constant, ATPChecker finds one piece of code that describes the data usage of var (line 21).…”
Section: Data Typementioning
confidence: 99%
See 1 more Smart Citation
“…Since the host apps share the same process space and permissions with TPLs, the mechanism violates the principle of least privilege, which leads to TPLs being over-privileged. Recent studies find that permission abuse allows TPLs to access users' personal information and causes potential privacy leakage [19]- [26]. In addition, the incorrect use of TPLs [26]- [28] may cause serious personal information leakage.…”
Section: Introductionmentioning
confidence: 99%