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 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| 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 |
|---|---|---|
Debian DLA |
DLA-88-1 | ruby1.8 security update |
Debian DLA |
DLA-235-1 | ruby1.9.1 security update |
EUVD |
EUVD-2011-2686 | The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID. |
Ubuntu USN |
USN-1377-1 | Ruby vulnerabilities |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.2% (2.248% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.