Ruby is vulnerable to information leakage. The attack is possible due to a flaw in the Ruby SecureRandom module. When using the SecureRandom.random_bytes class, the PRNG state was not modified after forking a child process. This could eventually lead to SecureRandom.random_bytes returning the same string more than once. An attacker keeping track of the strings returned by one child process could use this flaw to predict the strings SecureRandom.random_bytes would return in other child processes (as long as the parent process persisted
lists.fedoraproject.org/pipermail/package-announce/2011-July/063062.html
lists.fedoraproject.org/pipermail/package-announce/2011-July/063071.html
redmine.ruby-lang.org/issues/4579
svn.ruby-lang.org/cgi-bin/viewvc.cgi?view=revision&revision=32050
svn.ruby-lang.org/repos/ruby/tags/v1_8_7_352/ChangeLog
svn.ruby-lang.org/repos/ruby/tags/v1_9_2_290/ChangeLog
www.openwall.com/lists/oss-security/2011/07/11/1
www.openwall.com/lists/oss-security/2011/07/12/14
www.openwall.com/lists/oss-security/2011/07/20/1
www.openwall.com/lists/oss-security/2011/07/20/16
www.redhat.com/support/errata/RHSA-2011-1581.html
www.ruby-lang.org/en/news/2011/07/02/ruby-1-8-7-p352-released/
www.ruby-lang.org/en/news/2011/07/15/ruby-1-9-2-p290-is-released/
www.securityfocus.com/bid/49015
access.redhat.com/errata/RHSA-2011:1581
access.redhat.com/security/updates/classification/#low
bugzilla.redhat.com/show_bug.cgi?id=722415