yFuzz is a project for running fuzzing jobs at scale with Kubernetes.
Since Google open-sourced more of ClusterFuzz this project has been discontinued.
Popular fuzzers such as Libfuzzer and AFL have support for running multiple fuzzing processes at once. yFuzz aims to take advantage of this by running each process on a different Kubernetes pod to speed up the fuzzing process.
For open-source projects, this can be done with OSS-Fuzz, with some restrictions:
- The targeted project must be open-source
- The targeted project must have a significant user base, or be critical to the global IT infrastructure
yFuzz aims to be an on-premises solution for distributed fuzzing, so that projects that don't meet these constraints can still be fuzzed.
Additional features to make the fuzzing process easier are also planned, such as automatic generation/suggestion of fuzz targets. We welcome all feedback and suggestions as we consider other use-cases.
- yFuzz Server: The main API server for yFuzz.
- yFuzz CLI: A command-line interface for interacting with the yFuzz server.
- yFuzz Scripts: Docker image with scripts used by yFuzz containers.
The yFuzz API resides in a kubernetes cluster along with the pods that run the fuzzing jobs and a shared volume that holds corpus data to be shared between the pods.
cmd: Command line utilities.docs: Documentation relating to yFuzz.images: Dockerfiles used by yFuzz.pkg: Shared libraries and packages.scripts: Scripts for CI tooling.services: Long-running services, such as the yfuzz-server.
Please refer to the contributing.md file for information about how to get involved. We welcome issues, questions, and pull requests. Pull Requests are welcome
This project is licensed under the terms of the Apache 2.0 open source license.