xlxs4 / aflplusplus-util Goto Github PK

The AFL++ docs mention some tips. These are the best resource on how to structure the CI pipeline at a high level I could find. Beyond that. You can use a local CI runner; that would mean that not only can you have the CI to periodically fuzz your codebase (following the tips above) but also use the server for the high computational power needed to fuzz for extended periods of time.

So, this would mean in return that you can and should take advantage of <insert_your_CI_here> functionality to rewrite parts of the AFL++ template. For example, some of these scripts can become jobs/stages.

• Automate/Facilitate updating the aflplusplus Docker image
• Create custom Dockerfile based on the aflplusplus Docker image

• Some things we run here are not parallelized. They can be
• There's a lot of changes needed to increase/decrease the cores used and the fuzzer instances used. Currently, everything is hardcoded (e.g. hardcoded 2 fuzzer instances, one Main one Secondary; hardcoded launch-screen and quit-screen scripts...). Big room for improvement. Here is a brief rundown on using multiple cores with AFL++. afl-trivia, afl-extras, afl-utils can serve as great resources for inspiration. They can also help coming up with better helper scripts

Change ToTest.cpp code to have AFL++ use Shared memory fuzzing. C -> C++ adjustments must be made