Bug 722419 - CVE-2011-2686 ruby: Properly initialize the random number generator when forking new process [fedora-all]
CVE-2011-2686 ruby: Properly initialize the random number generator when fork...
Product: Fedora
Classification: Fedora
Component: ruby (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Jeroen van Meeuwen
Fedora Extras Quality Assurance
: Security, SecurityTracking
Depends On:
Blocks: CVE-2011-2686/CVE-2011-2705/CVE-2011-3009
  Show dependency treegraph
Reported: 2011-07-15 06:02 EDT by Jan Lieskovsky
Modified: 2011-08-01 03:13 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Release Note
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-08-01 03:13:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Lieskovsky 2011-07-15 06:02:16 EDT
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected Fedora

For comments that are specific to the vulnerability please use bugs filed
against "Security Response" product referenced in the "Blocks" field.

For more information see:

When creating a Bodhi update request, please include the bug IDs of the
respective parent bugs filed against the "Security Response" product.
Please mention CVE ids in the RPM changelog when available.

Bodhi update submission link:

Please note: this issue affects multiple supported versions of Fedora.
Only one tracking bug has been filed; please only close it when all
affected versions are fixed.

[bug automatically created by: add-tracking-bugs]
Comment 1 Fedora Update System 2011-07-15 21:49:42 EDT
ruby- has been submitted as an update for Fedora 15.
Comment 2 Fedora Update System 2011-07-15 21:49:43 EDT
ruby- has been submitted as an update for Fedora 14.
Comment 3 Mamoru TASAKA 2011-08-01 03:13:42 EDT
On Fedora side this is fixed.

Note You need to log in before you can comment on or make changes to this bug.