ruby: Properly initialize the random number generator when forking new process
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 4 | |||
| ruby-0:1.8.1-18.el4 | cpe:/o:redhat:enterprise_linux:4 | RHSA-2012:0070 | 2012-01-30T00:00:00Z |
| Red Hat Enterprise Linux 5 | |||
| ruby-0:1.8.5-22.el5_7.1 | cpe:/o:redhat:enterprise_linux:5 | RHSA-2012:0070 | 2012-01-30T00:00:00Z |
| Red Hat Enterprise Linux 6 | |||
| ruby-0:1.8.7.352-3.el6 | cpe:/o:redhat:enterprise_linux:6 | RHSA-2011:1581 | 2011-12-05T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2011-2977 | Ruby before 1.8.6-p114 does not reset the random seed upon forking, which makes it easier for context-dependent attackers to predict the values of random numbers by leveraging knowledge of the number sequence obtained in a different child process, a related issue to CVE-2003-0900. |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.0% (2.023% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.