googleprojectzero / googleprojectzero/Jackalope
"process dead" issue that is not occured by WinAFL or other Fuzzer
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Hello, I'm trying to use Jackalope, and I have a 'process death' issue that doesn't happen with winAFL or kAFL.
The fuzzer should be executed on the assumption that it is repeated and executed within the function fuzzme(), where Jackalope does not loop and the process 'dead'. It actually crash target process (WerFault.exe) and the target process dies.
What I suspect is that dlls that are targeting fuzzing will generate C++ exceptions (CPPEH), which JackAlpope does not seem to send to the original exception handler. I'm flustered that this problem hasn't happened with DynamicRIO or Host. What should I do in this case?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the process-death behavior in Jackalope when fuzzme() is executed repeatedly, noting the target crash in WerFault.exe. Compare the behavior with winAFL, kAFL, DynamicRIO, and Host, and investigate the reported C++ exception-handling difference. Done means identifying why the target process dies and documenting a verified fix or workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- security, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100