Banner object (1)

Hack and Take the Cash !

836 bounties in database
  Back Link to program      
RubyGems logo
Hall of Fame


500 $ 


Found a security issue with RubyGems or Please follow these steps to report it.

For bounty rewards, only the rubygems library is in scope.

Reporting a security issue

Before continuing, please ensure this is a security issue for the RubyGems client or the service. For all vulnerabilities with individual gems, follow our guide on reporting security issues __with others' gems. If it's a security issue with the Ruby on Rails framework, see the Rails Security guide __.

For any security bug or issue with the RubyGems client or service, please let us know here with details about the problem.

Please note: the rubygems-developers mailing list __, the mailing list __, and the #rubygems IRC channel are public areas. If escalating to these places, please do not discuss your issue, simply say that you’re trying to get a hold of someone from the security team. Thanks in advance for responsibly disclosing your security issue.

Reporting Website Problems

If you're having trouble pushing a gem, or otherwise need help with your account, please open a new help issue.

For bugs or other problems with, please use the help site to open a new issue __.

Disclosure Process

RubyGems and follow a 5 step disclosure process:

  1. Security report received and is assigned a primary handler. This person will coordinate the fix and release process.
  2. Problem is confirmed and, a list of all affected versions is determined. Code is audited to find any potential similar problems.
  3. Fixes are prepared for all releases which are still supported. These fixes are not committed to the public repository but rather held locally pending the announcement.
  4. A suggested embargo date for this vulnerability is chosen.
  5. On the embargo date, the rubygems-developers mailing list __is sent an announcement. This will include patches for all versions still under support. The changes are pushed to the public repository and new gems released to rubygems. At least 6 hours after the mailing list is notified, a copy of the advisory will be published on the blog __.

This process can take some time, especially when coordination is required with maintainers of other projects. Every effort will be made to handle the bug in as timely a manner as possible, however it’s important that we follow the release process above to ensure that the disclosure is handled in a consistent manner.

Disclosure Policy

  • Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.


While researching, we'd like to ask you to refrain from:

  • Denial of service
  • Spamming
  • Brute-force attacks
  • Social engineering (including phishing) of staff or volunteers
  • Any physical attempts against property or data centers
  • Using scanners or automated tools to find vulnerabilities - they’re noisy and lead to false positives

Receiving Security Updates

The best way to receive all the security announcements is to subscribe to the rubygems-developers mailing list __.

No one outside the core team or the initial reporter will be notified prior to the lifting of the embargo. We regret that we cannot make exceptions to this policy for high traffic or important sites, as any disclosure beyond the minimum required to coordinate a fix could cause an early leak of the vulnerability.

Internet Bug Bounty Qualification

For bounty rewards, only the rubygems library __is in scope. Also, only critical vulnerabilities that demonstrate complete compromise of the system's integrity or confidentiality are eligible for a bounty - typically Arbitrary Code Execution or equivalent impact. While we encourage you to submit all potential issues, lower severity issues are not in scope for the bounty at this time.

Impact | Amount
High Demonstrate that remote exploitation of this bug can be easily, actively, and reliably achieved. | $1,500+
Medium Demonstrate that remote exploitation of this bug is very likely (e.g. good control a register). | $1,000
Minimum Demonstrate the presence of a security bug with probable remote exploitation potential. | $500

The project maintainers have final decision on which issues constitute security vulnerabilities. The Internet Bug Bounty Panel __will respect their decision, and we ask that you do as well. It's important to keep in mind that not all submissions will qualify for a bounty, and that the decision to award a bounty is entirely at the discretion of the Panel.

Comments on this Policy

If you have any suggestions to improve this policy, please send an email to

Thank you for helping keep RubyGems and our users safe!

In Scope

Scope Type Scope Name

Malicious or compromised gem



Out of Scope

Scope Type Scope Name

This program have been found on Hackerone on 2019-08-08.

FireBounty © 2015-2019

Legal notices