The Continuing Arms Race: Code-Reuse Attacks and Defenses 2018
DOI: 10.1145/3129743.3129748
|View full text |Cite
|
Sign up to set email alerts
|

Code-pointer integrity

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
279
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 171 publications
(280 citation statements)
references
References 0 publications
1
279
0
Order By: Relevance
“…After a deep rethought on randomization mechanism, security exports proposed two defense mechanisms: Lifetime Randomization [33] and Code Pointer Integrity (CPI) [34]. The so-called Lifetime Randomization, is based on the fine-grained Randomization, additionally the running process can continuously change the order of inner instructions in its memory space which to ensure that the leaked code location information is invalid at the time of Control Flow Hijacking.…”
Section: Address Space Layout Randomizationmentioning
confidence: 99%
“…After a deep rethought on randomization mechanism, security exports proposed two defense mechanisms: Lifetime Randomization [33] and Code Pointer Integrity (CPI) [34]. The so-called Lifetime Randomization, is based on the fine-grained Randomization, additionally the running process can continuously change the order of inner instructions in its memory space which to ensure that the leaked code location information is invalid at the time of Control Flow Hijacking.…”
Section: Address Space Layout Randomizationmentioning
confidence: 99%
“…SFI achieves this by sandboxing all memory-writes by untrusted modules (e.g., [37,61]). CFI leverages control-flow guards to enforce atomic blocks that guard memory-writes (e.g., [20,34,41]). …”
Section: Trust Modelmentioning
confidence: 99%
“…OVT-IVT [6] improves performance by reorganizing vtables to permit quick validation as a simple bounds check. CPI [34] heuristically derives a set of sensitive pointers, and guards their integrity to prevent control-flow hijacking. CPS [34] optimizes CPI to improve overheads for programs with many virtual functions by instrumenting only code pointers, but at the expense of less security for vtable pointers exploited by confused deputy attacks.…”
Section: Vtable Protectionmentioning
confidence: 99%
“…The most recent contribution to this domain is CodePointer Integrity (CPI) [36]. With CPI, Kuznetsov et al isolate all sensitive pointers, which are defined recursively as code pointers and pointers to sensitive pointers.…”
Section: Custom Code Analysis and Code Generationmentioning
confidence: 99%