What problem does it solve? Learning to find memory corruption vulnerabilities requires structured, hands-on practice with real fuzzing tools, and most engineers lack a guided path from basic AFL++ runs to triaging crashes in production parsers. ## Core Features & Use Cases - Coverage-Guided Fuzzing Labs: Step-by-step AFL++ setup, instrumentation with sanitizers (ASAN/UBSAN), seed corpus generation, and parallel master/slave fuzzing campaigns. - Multiple Fuzzer Workflows: Covers AFL++ for whole programs, Google FuzzTest for in-process property-based fuzzing of C++ functions, and Honggfuzz, with guidance on when each fits. - Crash Triage and Real CVE Case Studies: Minimization with afl-tmin, clustering with casr-afl, and analysis of real bugs like CVE-2024-47606 (GStreamer) and CVE-2023-4863 (libWebP). - Use Case: A security engineer sets up a fuzzing campaign against an image parser, builds a minimized seed corpus, runs parallel AFL++ instances with sanitizers enabled, and triages the resulting crashes for exploitability. ## Quick Start Walk me through setting up AFL++ with AddressSanitizer to fuzz a C parser and triage any crashes it finds.