-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No path while fuzzing ChakraCore #5
Comments
Can you confirm that AFL++ finds paths on the same target binary? |
Yes, AFL++ works well with enlarging memory settings by using
|
I'll look into this later. Can you check if it works without the bitmap size changes? |
Still no path without bitmap size changes. |
I tried to compile chakracore with afl-clang-fast, but ran into some problems regarding the fact that it is split into the "ch" binary, and libChakraCore.so. Could you post your build steps in a reproducible way? |
I build ChakraCore with |
Cool, looking into it. Didn't see the --static flag. |
Ok I can reproduce this. Looking into it. |
Should be fixed by a132369, when porting the Forkserver we forgot to add the program path to the argument list, resulting in ch not receiving the input file path. Please verify and close this issue. |
Thanks for fixing! It works well now. |
Just a notification lol. |
Yeah, that's the "stability score" of AFL expressed... well... less optimally^^ If you see lots of these (with ch you will), that means the bitmap target is pretty nondeterministic. |
Nautilus cannot find any path while fuzzing ChakraCore with
grammars/javascript_new.py
.I set up nautilus with the instructions in README.md
Then I enlarged the size of bitmap to 1 << 20 and instrument ChakraCore with afl-clang-fast.
modified the
config.ron
atpathed file
forksrv/src/lib.rs
atFuzzer status
It cannot find any path during fuzzing. See following output.
My System Infomation
The text was updated successfully, but these errors were encountered: