ruzzy

Automate coverage-guided fuzzing of Ruby applications and C extensions with libFuzzer.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/amano--/call-center --skill ruzzy-amano
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ruzzy
Source: https://github.com/amano--/call-center/tree/main/.gemini/antigravity/skills/trailofbits-security/ruzzy
Command: npx skills add https://github.com/amano--/call-center --skill ruzzy-amano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers find bugs and security vulnerabilities in Ruby code, including native C extensions, by automatically generating diverse inputs to test code paths.

Core Features & Use Cases

  • Coverage-guided fuzzing: Identifies bugs by instrumenting code and prioritizing inputs that cover new execution paths.
  • Fuzzing Ruby C extensions: Specifically designed to test native extensions for memory corruption and undefined behavior.
  • Use Case: A developer is working on a Ruby gem with a complex C extension for parsing a custom data format. They use Ruzzy to automatically discover memory leaks or buffer overflows in the C extension before releasing the gem.

Quick Start

Use the ruzzy skill to fuzz the provided Ruby harness script.

Frequently Asked Questions about ruzzy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fuzz Ruby C extensions for memory corruption?

Fuzz Ruby C extensions for memory corruption by integrating libFuzzer to automatically generate targeted inputs and detect bugs. This approach uses coverage-guided fuzzing to explore new execution paths and identify vulnerabilities.

What is coverage-guided fuzzing in Ruby?

Coverage-guided fuzzing in Ruby instruments code to prioritize generated inputs that trigger new execution paths. This mechanism effectively uncovers hidden bugs by systematically exercising complex code branches within the application.

Do I need AddressSanitizer to fuzz Ruby code?

You need AddressSanitizer and UndefinedBehaviorSanitizer to fuzz Ruby code when detecting memory corruption and undefined behavior. These sanitizers require specific build flags and environment variable configurations to function properly.

Can I use libFuzzer to find security vulnerabilities in Ruby gems?

You can use libFuzzer integration to find security vulnerabilities in Ruby gems by automatically generating diverse inputs to test code paths. This process exposes memory leaks or buffer overflows before releasing the gem.

How do I set up a Ruby harness script for fuzzing?

Set up a Ruby harness script for fuzzing by providing it to the automated fuzzing process, which then uses libFuzzer to generate targeted inputs. This harness defines the specific code entry points to test for bugs.

What are the limitations of fuzzing Ruby native extensions?

Limitations of fuzzing Ruby native extensions include the strict requirement for specific build flags and environment variable configurations to enable sanitizer support. Without this precise setup, detection of memory corruption fails.