yFuzz is a project for running fuzzing jobs at scale with Kubernetes.

It is still in early development and not ready for general use.

• yFuzz
  • Table of Contents
  • Background
  • Projects
  • Architecture
    • Planned:
  • Directory Structure
  • Contribute
  • License

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.

• 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.

• Each fuzzing pod will have a logging sidecar which streams logs from the pod to a centralized logging service.
• The yFuzz API will have access to a data store with information about users, jobs, and crash files.

• 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.