Reporting Security Vulnerabilities
Please send an email to email@example.com when you think you have found a security vulnerability in JRuby or one of its associated libraries (such as the jruby-openssl gem). We will do our best to respond to you within 72 hours and work with you to fix and properly disclose the nature of the vulnerability. Please note that firstname.lastname@example.org is a private email address and email sent to it will not result in public disclosure.
The JRuby team will endeavor to follow these steps when handling reported vulnerabilities:
- Work with the reporter to determine the appropriate fix within 24-72 hours of the initial email report.
- Once the fix has been found, wait for an embargo period of 48 hours.
- After the embargo has passed, push out a new software release containing the fix.
- Send email announcement on jruby-user mailing list containing source patch for most recent release.
- Post an announcement on jruby.org and list below.
December 27, 2011 – JRuby 18.104.22.168
Recommended upgrade. Potential for DOS attacks with specially crafted large hash/parameter lists. See the announcement for details.
April 26, 2010 – JRuby 1.4.1
Recommended upgrade. Potential for XSS attacks on prior versions of JRuby. See the announcement for details.
December 7, 2009 – jruby-openssl 0.6
Recommended upgrade. Affects some applications that use OpenSSL::SSL::VERIFY_PEER mode and jruby-openssl 0.5.2 or earlier. See the announcement for details.