ruzzy

You can fuzz Ruby C extensions by using a coverage-guided approach built on libFuzzer with sanitizer integration. This technique requires writing a harness, building with a Clang toolchain, and running with LD_PRELOAD to detect memory corruption and undefined behavior crashes.

Coverage-guided fuzzing for Ruby applications is an automated testing technique that uses code coverage data to generate inputs that uncover crashes. Built on libFuzzer, it helps find memory-safety issues in both pure Ruby code and native C extensions early in development.

Yes, you need a Clang toolchain to build sanitizer-enabled Ruby and C extensions. Running the fuzzing campaign also requires using LD_PRELOAD to load ASan and UBSan libraries so the sanitizer can properly detect memory corruption and undefined behavior.

To set up a fuzzing harness for Ruby native extensions, install the required gem and follow provided tracer and harness patterns. These patterns guide you on how to feed inputs into pure Ruby code or native extensions for effective crash detection during your campaign.

Yes, you can integrate libFuzzer-based fuzzing into CI pipelines for robustness testing of gem ecosystems. By running sanitizer-enabled Ruby builds with your harness, you can automatically detect memory-safety issues and crashes in Ruby libraries during continuous integration.

Your Ruby fuzzing campaign needs LD_PRELOAD to load ASan and UBSan sanitizer libraries at runtime. Without this preload step, the sanitizer integration cannot properly detect memory corruption and undefined behavior crashes in your C extensions during the fuzzing process.