googleprojectzero / googleprojectzero/Jackalope
[-] PROGRAM ABORT : Repeatedly failed to deliver sample
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Hi Ivan,
Unfortunately am facing this issue where after 2 days of fuzzing am getting the following error with Jackalope exiting and
not saving the crash test case!
Exception at address 0000000076A39AFB
Exception in instrumented module xxx.dll
Code before:
99 2b c2 8b c8 d1 f9 8b c6 99
Code after:
f7 f9 8b b5 28 fd ff ff e9 38 00 00 00 8b 85 48
[!] WARNING: Error delivering sample, retrying with a clean target
[-] PROGRAM ABORT : Repeatedly failed to deliver sample Location : Fuzzer::TryReproduceCrash(), C:\Users\symeon\Desktop\Jackalope\fuzzer.cpp:300
Interesting enough, I was able to reproduce this issue with different samples where before exiting it did save
the crash and I can confirm it was a valid crash!
What's the best way to help you reproduce it? Any ideas why is this happening?
Thanks!
Edit: Yes can confirm if I load the input_1 from the output folder (last fuzzed file) will indeed crash my harness.
Edit2: Am able to reproduce this issue within seconds, perhaps I could send you my repro privately..
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 at Fuzzer::TryReproduceCrash() in fuzzer.cpp around line 300 and reproduce the abort with the reported harness or the input_1 file from the output folder. Trace the repeated sample-delivery failure and determine how a valid crash can be preserved instead of causing the abort. Done means the failure is reproducible and the intended crash output behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100