2015 IEEE/ACM 37th IEEE International Conference on Software Engineering 2015
DOI: 10.1109/icse.2015.61
|View full text |Cite
|
Sign up to set email alerts
|

Mining Apps for Abnormal Usage of Sensitive Data

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

3
210
0
3

Year Published

2015
2015
2023
2023

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 184 publications
(216 citation statements)
references
References 21 publications
3
210
0
3
Order By: Relevance
“…Recently, Avdiienko et al presented an approach [6] closely related to ours. Both their approach and ours take sensitive data flows as features for machine learning-based malware detection, and both rely on FlowDroid to extract sensitive data flows.…”
Section: Related Workmentioning
confidence: 99%
See 3 more Smart Citations
“…Recently, Avdiienko et al presented an approach [6] closely related to ours. Both their approach and ours take sensitive data flows as features for machine learning-based malware detection, and both rely on FlowDroid to extract sensitive data flows.…”
Section: Related Workmentioning
confidence: 99%
“…However, the potential component leaks (flows) introduced by advertisement libraries are separate from the actual app code. As shown in MUDFLOW [6], advertisement libraries are frequently used and their flows (PCLs) thus become "normal", diluting the impact of actual app flows. Therefore, we follow MUDFLOW's assumption that advertisement libraries are trustworthy and ignore all the PCLs taking place in advertisement libraries, allowing our study to focus on the actual app PCLs.…”
Section: A Pcleaks Settingsmentioning
confidence: 99%
See 2 more Smart Citations
“…Then, an ICC method startActivity is called, which switches the current execution from Activity1 to Activity2. Finally, in Activity2, the device id is retrieved and is eventually sent out of the device through sendTextMessage (lines [15][16][17] This privacy leak cannot be detected by intra-component analyzers such as FlowDroid [10], because the switching between Activity1 and Activity2 is unfortunately decided only by the system and it is non-trivial to obtain it directly at the code level [11], [12]. Therefore, in this work we present IccTA, a code instrumentation based approach, which modifies the code to be analyzed in a way that inter-component feature is mitigated.…”
Section: A Code Analysismentioning
confidence: 99%