2018
DOI: 10.1007/978-981-13-2423-9_7
|View full text |Cite
|
Sign up to set email alerts
|

Stateful Forward-Edge CFI Enforcement with Intel MPX

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2021
2021
2022
2022

Publication Types

Select...
2

Relationship

1
1

Authors

Journals

citations
Cited by 2 publications
(1 citation statement)
references
References 30 publications
0
1
0
Order By: Relevance
“…Such attacks can be easily detected by most CFI checks [1,16] as the arbitrary location is rarely a function entry point. To avoid detection by coarse-grained CFI checks [31], call-wrong-func hijacks a function pointer to another function while the function chosen by call-wrong-func-within-static-analysis also falls in the valid set of targets collected by static control-flow analyses (thus is detectable only to path-sensitive CFI defenses [35,111]).…”
Section: Call-wrong-func-within-static-analysis Call-wrong-func Call-...mentioning
confidence: 99%
“…Such attacks can be easily detected by most CFI checks [1,16] as the arbitrary location is rarely a function entry point. To avoid detection by coarse-grained CFI checks [31], call-wrong-func hijacks a function pointer to another function while the function chosen by call-wrong-func-within-static-analysis also falls in the valid set of targets collected by static control-flow analyses (thus is detectable only to path-sensitive CFI defenses [35,111]).…”
Section: Call-wrong-func-within-static-analysis Call-wrong-func Call-...mentioning
confidence: 99%