Fork server crashed with signal 11

[f.f.ru...@gmail.com]

Hello

I have faced  Fork server crashed with signal 11 problem when I fuzz busybox binary

How can I solve this issue, please help me!

sudo chroot . ./afl-fuzz -m none -t 800000+ -Q -i ./inputs -o ./outputs -x keywords /bin/busybox @@
[sudo] password for bek:
afl-fuzz 2.52b by <lca...@google.com>
[+] You have 1 CPU core and 0 runnable tasks (utilization: 0%).
[*] Setting up output directories...
[+] Output directory exists but deemed OK to reuse.
[*] Deleting old session data...
[+] Output dir cleanup successful.
[*] Scanning './inputs'...
[+] No auto-generated dictionary tokens to reuse.
[*] Creating hard links for all input files...
[*] Loading extra dictionary from 'keywords' (level 0)...
[+] Loaded 115 extra tokens, size range 4 B to 126 B.
[!] WARNING: Some tokens are relatively large (126 B) - consider trimming.
[*] Validating target binary...
[*] Attempting dry run with 'id:000000,orig:seed'...
dry run:./outputs/queue/id:000000,orig:seed
[*] Spinning up the fork server...

[-] Whoops, the target binary crashed suddenly, before receiving any input
from the fuzzer! There are several probable explanations:
- The binary is just buggy and explodes entirely on its own. If so, you
need to fix the underlying problem or find a better replacement.
- Less likely, there is a horrible bug in the fuzzer. If other options
fail, poke <lca...@coredump.cx> for troubleshooting tips.

[-] PROGRAM ABORT : Fork server crashed with signal 11
Location : init_forkserver(), afl-fuzz.c:2201

[Fayozbek Rustamov]

Even I use “-m none” it doesn’t help.

- what is the reason for “fork server crashed signal 11”?

- any suggestion to solve this problem?

Thank you very much for sharing your time 

--


You received this message because you are subscribed to the Google Groups "afl-users" group.


To unsubscribe from this group and stop receiving emails from it, send an email to afl-users+...@googlegroups.com.


To view this discussion on the web visit https://groups.google.com/d/msgid/afl-users/d4fbcbba-cab8-4c89-9135-00422bb0940fn%40googlegroups.com.

[dome...@gmail.com]

Hi,

first of all, the manpage indicates you'll have to run busybox like:

busybox <applet> [arguments...]

The execution with `busybox @@` will expand to something like `busybox .cur_input`, not a valid applet.

That being said, busybox should probably not segfault. Maybe debug that in gdb or use strace. 

Best

Dominik Maier