CVE-2015-5276
gcc: Predictable randomness from std::random_device
Overview
Description
The std::random_device class in libstdc++ in the GNU Compiler Collection (aka GCC) before 4.9.4 does not properly handle short reads from blocking sources, which makes it easier for context-dependent attackers to predict the random values via unspecified vectors.
Source: OX vulnerability database
Severity
5 · MEDIUM
CVSS 2.0 base score, scored by NVD.
- Access vector
- Network
- Access complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Weakness: CWE-200
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 5 fixes
Red Hat 1 release · 1 package
wont fix 1
cpp
| Release | Package | Fixed in |
|---|---|---|
| 7 | cpp +38 | wont fix |
openSUSE 1 release · 1 package
fixed 1
cpp5
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | cpp5 +90 | 5.4.1+r240125-1.5 | openSUSE-SU-2024:10542-1 |
ubuntu 3 releases · 2 packages
affected 3
gcc-4-8
gcc-msp430
| Release | Package | Fixed in |
|---|---|---|
| 18.04-ESM | gcc-4-8 +1 | affected |
| 20.04-ESM | gcc-msp430 | affected |
| 22.04 | gcc-msp430 | affected |
References
- lists.opensuse.org http://lists.opensuse.org/opensuse-updates/2015-11/msg00054.html
- lists.opensuse.org http://lists.opensuse.org/opensuse-updates/2016-04/msg00052.html
- www.securitytracker.com http://www.securitytracker.com/id/1034375
- access.redhat.com https://access.redhat.com/security/cve/CVE-2015-5276
- bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=1262846
- gcc.gnu.org https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65142
- gcc.gnu.org https://gcc.gnu.org/ml/gcc-patches/2015-09/msg01050.html
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2015-5276
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2015-5276
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.