Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Kailiang Ying

dblp:153/5839 · DBLP profile ↗
← Back
5ranked-venue papers
2as first author
0since 2021 · last 2019
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Security and privacy · 4 · 1 first-authorComputer networks · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Network and information security
3 papers
Systems and software security · 36% Web and mobile security · 30% Hardware security and side channels · 23%

Topics — the 6 heaviest of 7, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Systems and software security › operating system security
mobile OS security
0.312018
TruZ-Droid: Integrating TrustZone with Mobile Operating System · MobiSys 2018
Hardware security and side channels
trusted execution environments
0.312018
TruZ-Droid: Integrating TrustZone with Mobile Operating System · MobiSys 2018
Web and mobile security
mobile application security
0.212016
Life after App Uninstallation: Are the Data Still Alive? Data Residue Attacks on Android · NDSS 2016
Systems and software security › exploitation › injection attacks
code injection attack
0.212014
Code Injection Attacks on HTML5-based Mobile Apps: Characterization, Detection and Mitigation · CCS 2014
Web and mobile security › web security
cross-site scripting
0.212014
Code Injection Attacks on HTML5-based Mobile Apps: Characterization, Detection and Mitigation · CCS 2014
Blockchain and cryptocurrency security › smart contract security
vulnerability detection
0.112014
Code Injection Attacks on HTML5-based Mobile Apps: Characterization, Detection and Mitigation · CCS 2014

Methods — techniques the papers use, named apart from their topics

trustzone · 0.3OS-level TEE integration · 0.3empirical study · 0.2vulnerability detection · 0.2patch · 0.2
YearPublicationVenuePosition
2019 TruZ-View: Developing TrustZone User Interface for Mobile OS Using Delegation Integration Model
abstract
When OS and hypervisor are compromised, mobile devices currently provide a hardware protected mode called Trusted Execution Environment (TEE) to guarantee the confidentiality and integrity of the User Interface (UI). The present TEE UI solutions adopt a self-contained design model, which provides a fully functional UI stack in the TEE, but they fail to manage one critical design principle of TEE: a small Trusted Computing Base (TCB), which should be more easily verified in comparison to a rich OS. The TCB size of the self-contained model is large as a result of the size of an individual UI stack. To reduce the TCB size of the TEE UI solution, we proposed a novel TEE UI design model called delegation model. To be specific, our design reuses the majority of the rich OS UI stack. Unlike the existing UI solutions protecting 3-dimensional UI processing in the TEE, our design protects the UI solely as a 2-dimensional surface and thus reduces the TCB size. Our system, called TruZ-View, allows application developers to use the rich OS UI development environment to develop TEE UI with consistent UI looks across the TEE and the rich OS. We successfully implemented our design on HiKey board. Moreover, we developed several TEE UI use cases to protect the confidentiality and integrity of UI. We performed a thorough security analysis to prove the security of the delegation UI model. Our real-world application evaluation shows that developers can leverage our TEE UI with few changes to the existing app's UI logic.
Kailiang Ying, Priyank Thavai, Wenliang Du 0001
CODASPY1
2018 TruZ-Droid: Integrating TrustZone with Mobile Operating System
abstract
Mobile devices today provide a hardware-protected mode called Trusted Execution Environment (TEE) to help protect users from a compromised OS and hypervisor. Today TEE can only be leveraged either by vendor apps or by developers who work with the vendor. Since vendors consider third-party app code untrusted inside the TEE, to allow an app to leverage TEE, app developers have to write the app code in a tailored way to work with the vendor's SDK. We proposed a novel design to integrate TEE with mobile OS to allow any app to leverage the TEE. Our design incorporates TEE support at the OS level, allowing apps to leverage the TEE without adding app-specific code into the TEE, and while using existing interface to interact with the mobile OS. We implemented our design, called TruZ-Droid, by integrating TrustZone TEE with the Android OS. TruZ-Droid allows apps to leverage the TEE to protect the following: (i) user's secret input and confirmation, and (ii) sending of user's secrets to the authorized server. We built a prototype using the TrustZone-enabled HiKey board to evaluate our design. We demonstrated TruZ-Droid's effectiveness by adding new security features to existing apps to protect user's sensitive information and attest user's confirmation. TruZ-Droid's real-world use case evaluation shows that apps can leverage TrustZone while using existing OS APIs. Our usability study proves that users can correctly interact with TruZ-Droid to protect their security sensitive activities and data.
Kailiang Ying, Amit Ahlawat, Bilal Alsharifi, Yuexin Jiang, Priyank Thavai, Wenliang Du 0001
MobiSys1
2016 Hey, You, Get Off of My Image: Detecting Data Residue in Android Images
Yousra Aafer, Kailiang Ying, Wenliang Du 0001
ESORICS (1)3
2016 Life after App Uninstallation: Are the Data Still Alive? Data Residue Attacks on Android
Kailiang Ying, Yousra Aafer, Zhenshen Qiu, Wenliang Du 0001
NDSS2
2014 Code Injection Attacks on HTML5-based Mobile Apps: Characterization, Detection and Mitigation
abstract
Due to the portability advantage, HTML5-based mobile apps are getting more and more popular.Unfortunately, the web technology used by HTML5-based mobile apps has a dangerous feature, which allows data and code to be mixed together, making code injection attacks possible. In this paper, we have conducted a systematic study on this risk in HTML5-based mobile apps. We found a new form of code injection attack, which inherits the fundamental cause of Cross-Site Scripting attack~(XSS), but it uses many more channels to inject code than XSS. These channels, unique to mobile devices, include Contact, SMS, Barcode, MP3, etc. To assess the prevalence of the code injection vulnerability in HTML5-based mobile apps, we have developed a vulnerability detection tool to analyze 15,510 PhoneGap apps collected from Google Play. 478 apps are flagged as vulnerable, with only 2.30\% false-positive rate. We have also implemented a prototype called NoInjection as a Patch to PhoneGap in Android to defend against the attack.
Xunchao Hu, Kailiang Ying, Wenliang Du 0001, Heng Yin 0001, Gautam Nagesh Peri
CCS3