LibAFL-legacy
LibAFL-legacy copied to clipboard
AFLplusplus
AFL++ as a library: gives you all the tools necessary to craft the best fuzzer for your targets with ease!
Wrote a harness to fuzz a lib using LibAFL. I get a crash within LibAFL, but cannot reproduce it outside LibAFL (almost identical harness ... outside LibAFL I added just...
If libafl has to be multi platform, we cannot really use just GNU makefiles. I propose meson as it was recently adopted by QEMU it and seems a sane build...
The main feature lacking in LibAFL right now is Extas support. This includes the dictionary extras, you would pass to AFL using `-x`, but also autoextras added during fuzzing, as...
Right now all doc is inside the code. We should set up a [sphinx instance](https://www.sphinx-doc.org/en/master/) or some other nice way to make the API browseable. To get started with sphinx,...
Right now LibAFL only supports its own, internal, mutators at build time. It may be beneficial to add a wrapper around the current mutators that can interface with existing Custom...
A fuzzer can look for something different than crashes. Think about timeouts for instance. The oracle class looks at observation channels, similarly to feedback, but it decides if the testcase...
Right now, we don't have any CI for LibAFL. However, we do have unittests and examples that can pose as test cases. These should be added to Travis, similar to...
We have entities (eg executor) and for each entity we will provide some implementations into libafl (eg inmemoryexecutor and forkserverexecutor). These implementations are part of the library, they should not...
Metadata
Owner
Metadata
AFL++ as a library: gives you all the tools necessary to craft the best fuzzer for your targets with ease!