libssh: Improper initialization of PRNG after fork()
Published Mar 14, 2014
1.9
LOWCVSS 2.0
EPSS 0.36%
Description
The RAND_bytes function in libssh before 0.6.3, when forking is enabled, does not properly reset the state of the OpenSSL pseudo-random number generator (PRNG), which causes the state to be shared between children processes and allows local users to obtain sensitive information by leveraging a pid collision.
Affected products
No data.
- ≤ 0.6.2
- 0.4.7
- 0.4.8
- 0.5.0
- 0.5.0
- 0.5.1
- 0.5.2
- 0.5.3
- 0.5.4
- 0.5.5
- 0.6.0
- 0.6.1
No data.
Red Hat Enterprise Linux 6
libssh2
Not affected
Red Hat Enterprise Linux 7
libssh2
Not affected
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 6 | libssh2 | Not affected | n/a |
| Red Hat Enterprise Linux 7 | libssh2 | Not affected | n/a |
No package ranges for this CVE.
Remediation
Red Hat statement
Not Vulnerable. This issue does not affect the version of libssh2 package as shipped with Red Hat Enterprise Linux 5 and 6.
Metrics
No CVSS v4.0 score for this CVE.
No CVSS v3.1 score for this CVE.
No CVSS v3.0 score for this CVE.
AV:L/AC:M/Au:N/C:P/I:N/A:N
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2022–2026- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Percentile over time
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Table of values (9 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 0.36% (0.00356) | 26.93th | v5 (v2026.06.15) |
| Jun 15, 2026 | 0.36% (0.00356) | 27.23th | v5 (v2026.06.15) |
| Mar 17, 2025 | 0.04% (0.00043) | 10.32th | v4 (v2025.03.14) |
| Dec 12, 2024 | 0.04% (0.00042) | 5.07th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.04% (0.00042) | 5.63th | v3 (v2023.03.01) |
| Mar 6, 2023 | 1.10% (0.01104) | 54.09th | v2 (v2022.01.01) |
| Sep 17, 2022 | 1.10% (0.01104) | 52.45th | v2 (v2022.01.01) |
| Apr 1, 2022 | 1.10% (0.01104) | 50.41th | v2 (v2022.01.01) |
| Feb 4, 2022 | 1.10% (0.01104) | 28.85th | v2 (v2022.01.01) |
References (11)
- http://lists.opensuse.org/opensuse-updates/2014-03/msg00036.html vendor-advisoryx_refsource_SUSE
- http://lists.opensuse.org/opensuse-updates/2014-03/msg00040.html vendor-advisoryx_refsource_SUSE
- http://secunia.com/advisories/57407 third-party-advisoryx_refsource_SECUNIAVendor Advisory
- http://www.debian.org/security/2014/dsa-2879 vendor-advisoryx_refsource_DEBIAN
- http://www.libssh.org/2014/03/04/libssh-0-6-3-security-release/ x_refsource_CONFIRMPatchVendor Advisory
- http://www.openwall.com/lists/oss-security/2014/03/05/1 mailing-listx_refsource_MLIST
- http://www.ubuntu.com/usn/USN-2145-1 vendor-advisoryx_refsource_UBUNTU
- https://access.redhat.com/security/cve/CVE-2014-0017 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1072191 x_refsource_CONFIRMIssue Tracking
- https://nvd.nist.gov/vuln/detail/CVE-2014-0017
- https://www.cve.org/CVERecord?id=CVE-2014-0017
| Link | Providers | Tags |
|---|---|---|
| http://lists.opensuse.org/opensuse-updates/2014-03/msg00036.html | vendor-advisoryx_refsource_SUSE | |
| http://lists.opensuse.org/opensuse-updates/2014-03/msg00040.html | vendor-advisoryx_refsource_SUSE | |
| http://secunia.com/advisories/57407 | third-party-advisoryx_refsource_SECUNIAVendor Advisory | |
| http://www.debian.org/security/2014/dsa-2879 | vendor-advisoryx_refsource_DEBIAN | |
| http://www.libssh.org/2014/03/04/libssh-0-6-3-security-release/ | x_refsource_CONFIRMPatchVendor Advisory | |
| http://www.openwall.com/lists/oss-security/2014/03/05/1 | mailing-listx_refsource_MLIST | |
| http://www.ubuntu.com/usn/USN-2145-1 | vendor-advisoryx_refsource_UBUNTU | |
| https://access.redhat.com/security/cve/CVE-2014-0017 | Vendor Advisory | |
| https://bugzilla.redhat.com/show_bug.cgi?id=1072191 | x_refsource_CONFIRMIssue Tracking | |
| https://nvd.nist.gov/vuln/detail/CVE-2014-0017 | ||
| https://www.cve.org/CVERecord?id=CVE-2014-0017 |
Change history (0)
No recorded changes yet.