2018 17th IEEE International Conference on Trust, Security and Privacy in Computing and Communications/ 12th IEEE International 2018
DOI: 10.1109/trustcom/bigdatase.2018.00141
|View full text |Cite
|
Sign up to set email alerts
|

SDLI: Static Detection of Leaks Across Intents

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
2
1
1
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(3 citation statements)
references
References 16 publications
0
3
0
Order By: Relevance
“…Another static analysis tool, SDLI [28], built on top of a commercial static analyzer Julia and not publicly available, it generates XML reports for each inward and outward intent and compares XMLs reports for intent leakage. Their work is similar to ours but in our work, we are considering threat models discussed in section 3.1 that are possible with broadcast receivers.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Another static analysis tool, SDLI [28], built on top of a commercial static analyzer Julia and not publicly available, it generates XML reports for each inward and outward intent and compares XMLs reports for intent leakage. Their work is similar to ours but in our work, we are considering threat models discussed in section 3.1 that are possible with broadcast receivers.…”
Section: Related Workmentioning
confidence: 99%
“…This Constant class is in Constant2 which is in Constant3. We create double chain references for public class variable as seen in line 19 and 20, which can match double, triple or higher level chained reference as seen in line 22-25 and we create static variable chain reference with class name as shown in line 28 Despite all these rules, Our static analysis can still contain LBM instances. As discussed in section 4.1, any source files unable to parse by TXL compiler were discarded if any of those files containing the LBM instances then they were missed during the analysis and can be marked as insecure.…”
Section: Rules To Address Chained and Static Lbm Instancesmentioning
confidence: 99%
“…The Julia analyser library provides a representation of Java bytecode which is suitable for interpretation (Mandal, Cortesi, Ferrara, Panarotto, & Spoto, 2018). Julia analyses the Java source code, which are already complied into Java bytecode inside Android Studio [12].…”
Section: F Safeguardmentioning
confidence: 99%