RubyGems Vulnerability Disclosure Program

Program Overview

RubyGems runs a vulnerability disclosure program on HackerOne. The program has 4 in-scope assets.

In-Scope Assets

Asset	Type	Max Severity	Eligible
Malicious or compromised gem	OTHER	High	No Bounty
https://github.com/rubygems/rubygems	SOURCE_CODE	Critical	No Bounty
rubygems.org	URL	Critical	No Bounty
shipit.rubygems.org	URL	Critical	No Bounty

Out-of-Scope Assets

• blog.rubygems.org
• guide.rubygems.org
• help.rubygems.org
• http://rubygems.org/names
• https://s3-us-west-2.amazonaws.com/rubygems-dumps
• stats.rubygems.org
• status.rubygems.org
• support.rubygems.org
• uptime.rubygems.org

Tips for Hacking RubyGems

1. Read the policy — Understand what's in scope, out of scope, and any specific testing restrictions before you start.
2. Enumerate the attack surface — Use subdomain enumeration and directory bruteforcing to map all accessible endpoints.
3. Focus on high-impact bugs — Look for SQL injection, SSRF, and IDOR vulnerabilities first.
4. Test authentication flows — Check for OAuth misconfigurations and CSRF in login/signup flows.
5. Write clear reports — Include steps to reproduce, impact assessment, and suggested remediation. Use Burp Suite to capture evidence.

Frequently Asked Questions

How do I start hacking RubyGems?

Sign up on HackerOne, read the program policy carefully, review the in-scope assets listed above, and start testing. Always stay within scope and follow responsible disclosure guidelines.

Does RubyGems pay bounties?

No, RubyGems runs a Vulnerability Disclosure Program (VDP) without monetary rewards. You may receive recognition or swag.

What types of vulnerabilities does RubyGems accept?

RubyGems accepts reports for vulnerabilities found in their 4 in-scope assets. Common accepted vulnerability types include XSS, SQL injection, SSRF, IDOR, authentication bypass, and RCE. Check the program policy for specific exclusions.