2018
DOI: 10.1007/978-3-319-99073-6_18
|View full text |Cite
|
Sign up to set email alerts
|

PwIN – Pwning Intel piN: Why DBI is Unsuitable for Security Applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
30
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 14 publications
(32 citation statements)
references
References 20 publications
0
30
0
Order By: Relevance
“…Supporting the first property in the presence of a dedicated adversary seems instead hard for a DBI engine: as the runtime shares the same address space of the code under analysis, the possibility of covert channels is real. Actually, by subverting isolation an attacker might in turn also foil the inspection and interposition capabilities of a DBI system [28].…”
Section: Desired Transparency Propertiesmentioning
confidence: 99%
See 4 more Smart Citations
“…Supporting the first property in the presence of a dedicated adversary seems instead hard for a DBI engine: as the runtime shares the same address space of the code under analysis, the possibility of covert channels is real. Actually, by subverting isolation an attacker might in turn also foil the inspection and interposition capabilities of a DBI system [28].…”
Section: Desired Transparency Propertiesmentioning
confidence: 99%
“…There are peculiarities of DBI that could be exploited as well: for instance, the time required to dynamically load a library from user code can be two orders of magnitude larger [17] under DBI due to the image loading process. Similarly, effects of the trace compilation process can be exploited by observing fluctuations in the time required to take a branch in the program from the first time it is observed in the execution [28].…”
Section: Artifacts In Current Dbi Embodimentsmentioning
confidence: 99%
See 3 more Smart Citations