2022
DOI: 10.1016/j.eswa.2022.118298
|View full text |Cite
|
Sign up to set email alerts
|

ObfSec: Measuring the security of obfuscations from a testing perspective

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2023
2023
2023
2023

Publication Types

Select...
1

Relationship

1
0

Authors

Journals

citations
Cited by 1 publication
(1 citation statement)
references
References 23 publications
0
1
0
Order By: Relevance
“…However the same combination of program and bad input led to the program, on reaching line 11 when run on a native X86 being terminated with a segmentation fault (LLM-generated program executed as ./00172.c.o 0; available at [2]). It appears that the address space of gem5 might mask these kinds of pointer errors, similarly to what happens with virtualization for obfuscations [15], where invalid addresses that normally belong to the operating system are part of the process address space. Portability AFL++ has been applied to various targets [1,12,16,17] and hence a different target SUT should be easy.…”
Section: Resultsmentioning
confidence: 97%
“…However the same combination of program and bad input led to the program, on reaching line 11 when run on a native X86 being terminated with a segmentation fault (LLM-generated program executed as ./00172.c.o 0; available at [2]). It appears that the address space of gem5 might mask these kinds of pointer errors, similarly to what happens with virtualization for obfuscations [15], where invalid addresses that normally belong to the operating system are part of the process address space. Portability AFL++ has been applied to various targets [1,12,16,17] and hence a different target SUT should be easy.…”
Section: Resultsmentioning
confidence: 97%