4. Download Your Bugs
You can list the bugs you found and download them from the web site.
Note that your bug can be automatically reported to developers (with your credit).
The bug file you download is essentially libfuzzer's input file.
To test/reproduce your bug, the best way is connecting inside your docker container as below.
1. `sudo docker ps` to get your running container ID.
2. `sudo docker exec -it [your_container_id] bash` to get inside docker container.
3. inside docker, you will see a file starting with `crash-` prefix (if you found crash).
4. run `/target.bin /crash-xxxxxxxxxxxxxxxxx` to reproduce crash and see ASAN result.
* You can extract the `target.bin` (libfuzzer binary) to your host and try the same thing
but if there is mismatch in environment (e.g., library) you might fail to reproduce crash.
* If you kill your docker and restart, put your crash input inside docker (via shared folder),
your fuzzer `target.bin` might be changed into different version
thus fail to reproduce the crash (some projects has multiple versions of `target.bin`, e,g, 10 or 100).
So, it is best not to exit your docker since the moment you found crash (to maintain same environment).
For some projects, you might get the different version of `target.bin` when you restart your docker container.
As an alternative, you can download fuzzer binaries from each project pages and feed your crash input to all of them.
If you have trouble reproducing the bug, contact admin for support.