Fork server crashed with signal 11 while fuzz jhead

[gjduck]

Fork server crashed with signal 11 while fuzz jhead

[Sunxingzhezhexingsun]

In addition, I used AFL-gcc to compile and then use AFL-fuzz to test, the result is normal, no errors.

[Sunxingzhezhexingsun]

This does seem to be a memory limitation issue about AFL, I use the following command and everything works fine !

root@ubuntu-lzx:~/fuzz/e9afl-jhead# ./afl-fuzz -m 10G -i in -o out -- ./jhead.afl @@
afl-fuzz 2.57b by <[email protected]>
[+] You have 16 CPU cores and 1 runnable tasks (utilization: 6%).
[+] Try parallel jobs - see docs/parallel_fuzzing.txt.
[*] Checking CPU core loadout...
[+] Found a free CPU core, binding to #0.
[*] Checking core_pattern...
[*] Setting up output directories...
[+] Output directory exists but deemed OK to reuse.
[*] Deleting old session data...
[+] Output dir cleanup successful.
[*] Scanning 'in'...
[+] No auto-generated dictionary tokens to reuse.
[*] Creating hard links for all input files...
[*] Validating target binary...
[*] Attempting dry run with 'id:000000,orig:badyear.jpg'...
[*] Spinning up the fork server...
[+] All right - fork server is up.
    len = 19379, map size = 509, exec speed = 691 us
[+] All test cases processed.

[!] WARNING: Some test cases are big (18.9 kB) - see docs/perf_tips.txt.
[+] Here are some useful stats:

    Test case count : 1 favored, 0 variable, 1 total
       Bitmap range : 509 to 509 bits (average: 509.00 bits)
        Exec timing : 691 to 691 us (average: 691 us)

[*] No -t option specified, so I'll use exec timeout of 20 ms.
[+] All set and ready to roll!

[GJDuck]

Yes, AFL will crash-by-default which is unfortunate. There is not much that can be done, other than to document the problem and how to fix it.