{"title":"进程间隔离的持久内存安全威胁","authors":"Naveed Ul Mustafa, Yan Solihin","doi":"10.1109/MM.2023.3264938","DOIUrl":null,"url":null,"abstract":"Persistent memory object (PMO) is a general system abstraction for holding persistent data in persistent main memory, managed by an operating system. A PMO programming model breaks interprocess isolation as it results in the sharing of persistent data between two processes as they alternatively access the same PMO. In this article, we discuss security implications of a PMO model. We demonstrate that the model enables one process to affect execution of another process, even without sharing a PMO over time. This allows an adversary to launch inter-PMO security attacks if two processes are linked via other unshared PMOs. We present formalization of inter-PMO attacks, their examples, and potential strategies to defend against them.","PeriodicalId":13100,"journal":{"name":"IEEE Micro","volume":"43 1","pages":"16-23"},"PeriodicalIF":2.8000,"publicationDate":"2023-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Persistent Memory Security Threats to Interprocess Isolation\",\"authors\":\"Naveed Ul Mustafa, Yan Solihin\",\"doi\":\"10.1109/MM.2023.3264938\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Persistent memory object (PMO) is a general system abstraction for holding persistent data in persistent main memory, managed by an operating system. A PMO programming model breaks interprocess isolation as it results in the sharing of persistent data between two processes as they alternatively access the same PMO. In this article, we discuss security implications of a PMO model. We demonstrate that the model enables one process to affect execution of another process, even without sharing a PMO over time. This allows an adversary to launch inter-PMO security attacks if two processes are linked via other unshared PMOs. We present formalization of inter-PMO attacks, their examples, and potential strategies to defend against them.\",\"PeriodicalId\":13100,\"journal\":{\"name\":\"IEEE Micro\",\"volume\":\"43 1\",\"pages\":\"16-23\"},\"PeriodicalIF\":2.8000,\"publicationDate\":\"2023-09-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"IEEE Micro\",\"FirstCategoryId\":\"94\",\"ListUrlMain\":\"https://doi.org/10.1109/MM.2023.3264938\",\"RegionNum\":3,\"RegionCategory\":\"计算机科学\",\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"Q2\",\"JCRName\":\"COMPUTER SCIENCE, HARDWARE & ARCHITECTURE\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"IEEE Micro","FirstCategoryId":"94","ListUrlMain":"https://doi.org/10.1109/MM.2023.3264938","RegionNum":3,"RegionCategory":"计算机科学","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"Q2","JCRName":"COMPUTER SCIENCE, HARDWARE & ARCHITECTURE","Score":null,"Total":0}
Persistent Memory Security Threats to Interprocess Isolation
Persistent memory object (PMO) is a general system abstraction for holding persistent data in persistent main memory, managed by an operating system. A PMO programming model breaks interprocess isolation as it results in the sharing of persistent data between two processes as they alternatively access the same PMO. In this article, we discuss security implications of a PMO model. We demonstrate that the model enables one process to affect execution of another process, even without sharing a PMO over time. This allows an adversary to launch inter-PMO security attacks if two processes are linked via other unshared PMOs. We present formalization of inter-PMO attacks, their examples, and potential strategies to defend against them.
期刊介绍:
IEEE Micro addresses users and designers of microprocessors and microprocessor systems, including managers, engineers, consultants, educators, and students involved with computers and peripherals, components and subassemblies, communications, instrumentation and control equipment, and guidance systems. Contributions should relate to the design, performance, or application of microprocessors and microcomputers. Tutorials, review papers, and discussions are also welcome. Sample topic areas include architecture, communications, data acquisition, control, hardware and software design/implementation, algorithms (including program listings), digital signal processing, microprocessor support hardware, operating systems, computer aided design, languages, application software, and development systems.