ruzzy

Automates coverage-guided fuzz testing of Ruby code and C extensions with ASan/UBSan.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/keremtoker468-dotcom/restoran --skill ruzzy-keremtoker468-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ruzzy
Source: https://github.com/keremtoker468-dotcom/restoran/tree/main/.claude/skills/ruzzy
Command: npx skills add https://github.com/keremtoker468-dotcom/restoran --skill ruzzy-keremtoker468-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a coverage-guided fuzzer specifically designed for Ruby, enabling the discovery of memory corruption and undefined behavior bugs in both pure Ruby code and native C extensions.

Core Features & Use Cases

  • Fuzzing Ruby: Test Ruby applications and libraries for vulnerabilities.
  • C Extension Safety: Detect memory safety issues in Ruby C extensions.
  • Sanitizer Support: Integrates AddressSanitizer (ASan) and UndefinedBehaviorSanitizer (UBSan).
  • Use Case: You have a critical Ruby gem with a C extension that handles user-uploaded data. Use Ruzzy to fuzz the C extension's parsing logic to find and fix potential memory leaks or buffer overflows before they can be exploited.

Quick Start

Use the ruzzy skill to fuzz the provided Ruby harness script 'fuzz_target.rb'.

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 bugs?

Fuzz Ruby C extensions for memory corruption by using a coverage-guided fuzzer that integrates AddressSanitizer to detect buffer overflows and leaks during automated test input generation.

What is coverage-guided fuzzing for Ruby code?

Coverage-guided fuzzing for Ruby code is an automated testing technique that monitors execution paths to generate targeted inputs, discovering undefined behavior and memory bugs in pure Ruby scripts and C extensions.

Can I use AddressSanitizer and UndefinedBehaviorSanitizer with Ruby fuzzing?

AddressSanitizer and UndefinedBehaviorSanitizer integrate directly with Ruby fuzzing to detect memory corruption and undefined behavior, targeting vulnerabilities in both pure Ruby code and native C extensions.

How do I find undefined behavior in Ruby gems handling user-uploaded data?

Find undefined behavior in Ruby gems handling user-uploaded data by fuzzing the parsing logic with UndefinedBehaviorSanitizer integration, identifying potential memory leaks and buffer overflows before exploitation.

Does fuzzing pure Ruby code require a C compiler with sanitizer support?

Fuzzing pure Ruby code uses a tracer script approach for coverage guidance, while direct fuzzing of C extensions requires sanitizer integration to detect memory corruption and undefined behavior.

Why use a Ruby fuzzer instead of standard unit tests for C extension safety?

A Ruby fuzzer automates input generation using coverage guidance to explore edge cases that standard unit tests miss, actively detecting memory corruption and undefined behavior via sanitizer integration.