Rubymem

Providing memory resources for the Ruby community.
Follow us @memruby or email us via info at rubymem.com

Advisory form

The name of the gem, as seen in Rubygems.
The date this leak was disclosed to the library author or community.
A link to a blog post, mailing list, github issue, etc that describes this vulnerability.
A short sentence: what kind of bug affects what gem?
One or two paragraphs describing the issue. A good description explains what the flaw is, and why the reader should care. A great description provides more context and possible workarounds.
Are there versions of this gem that are unaffected by the vulnerability?

Please provide line separated Gem version requirements. Use any operator as appropriate, including the pessimistic one.
Has the library released any patches?

Please provide line separated Gem version requirements. Use any operator as appropriate, including the pessimistic one.
Any additional links that might provide more context, i.e. github commits.
We might have to contact you in case things are unclear.

Report a new leak

Hey! Thanks for taking the time to do this. Your submission helps the community. All submissions to this website are ultimately vetted on the GitHub repository.

Reporting a leak takes three steps.

  1. Fill out the form to the left.
  2. Review the preview. We turn your report into the YAML that goes into the advisory database, so you can revise anything that looks out of place.
  3. Submit for review. That is when we store it and email the reviewers, nothing is saved before it.

Before you start

  • If it is a vulnerability, discreetly disclose the flaw to the gem maintainer(s) first. Please be polite! Open source maintainers are usually unpaid volunteers, and everyone deserves a little courtesy.
  • Try to figure out what versions are affected by the flaw, and whether a patch can be released.