Commercial hypervisor-based task sandboxing mechanisms are unsecured? But we can fix it!

Dongdong Huo, Chen Cao, Peng Liu, Yazhe Wang, Mingxuan Li, Zhen Xu

Research output: Contribution to journalArticlepeer-review

2 Scopus citations

Abstract

Cyber–Physical–Social Systems are frequently prescribed for providing valuable information on personalized services. The foundation of these services is big data which must be trustily collected and efficiently processed. Though High Performance Computing and Communication technique makes great contributions to addressing the issue of data processing, its effectiveness still relies on the veracity of data generated from Internet of Things (IoT) devices. Nevertheless, IoT devices, as basic production facilities to ensure data's security, are unable to deploy expensive security extensions. Consequently, it causes the implementation of the task sandboxing, the fundamental security mechanism in Real-Time Operating Systems (RTOSs), much simpler and more vulnerable. In this paper, we take ARM Mbed uVisor as an example system, utilizing hypervisor-based task sandboxing mechanisms, and presents three new findings: First, we discover vulnerabilities against Mbed task sandboxing, which can be exploited to compromise system-maintained data structure to manipulate any tasks’ data. Second, we present LIPS (Lightweight Intra-Mode Privilege Separation), building a special protection domain to isolate particular system-maintained data structures. Finally, thorough evaluation and experimental tests show the efficiency of LIPS to defeat these attacks, with small runtime overheads and good portability.

Original languageEnglish (US)
Article number102114
JournalJournal of Systems Architecture
Volume116
DOIs
StatePublished - Jun 2021

All Science Journal Classification (ASJC) codes

  • Software
  • Hardware and Architecture

Fingerprint

Dive into the research topics of 'Commercial hypervisor-based task sandboxing mechanisms are unsecured? But we can fix it!'. Together they form a unique fingerprint.

Cite this