medium
4.3
CWE
332
Advisory Published
CVE Published
Updated

CVE-2014-0016

First published: Tue Mar 04 2014(Updated: )

A flaw was found in the way stunnel, a socket wrapper which can provide SSL support to ordinary applications, performed (re)initialization of PRNG after fork. When accepting a new connection, the server forks and the child process handles the request. The RAND_bytes() function of openssl doesn't reset its state after the fork, but seeds the PRNG with the output of time(NULL). The most important consequence is that servers using EC (ECDSA) or DSA certificates may under certain conditions leak their private key.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
stunnel<=4.56
stunnel=0.1
stunnel=1.0
stunnel=1.1
stunnel=1.2
stunnel=1.3
stunnel=1.4
stunnel=1.5
stunnel=1.6
stunnel=2.0
stunnel=2.1
stunnel=3.0
stunnel=3.0-b1
stunnel=3.0-b2
stunnel=3.0-b3
stunnel=3.0-b4
stunnel=3.0-b5
stunnel=3.0-b6
stunnel=3.0-b7
stunnel=3.1
stunnel=3.2
stunnel=3.3
stunnel=3.4a
stunnel=3.5
stunnel=3.6
stunnel=3.7
stunnel=3.8
stunnel=3.8-p1
stunnel=3.8-p2
stunnel=3.8-p3
stunnel=3.8-p4
stunnel=3.8p1
stunnel=3.8p2
stunnel=3.8p3
stunnel=3.8p4
stunnel=3.9
stunnel=3.10
stunnel=3.11
stunnel=3.12
stunnel=3.13
stunnel=3.14
stunnel=3.15
stunnel=3.16
stunnel=3.17
stunnel=3.18
stunnel=3.19
stunnel=3.20
stunnel=3.21
stunnel=3.21a
stunnel=3.21b
stunnel=3.21c
stunnel=3.22
stunnel=3.23
stunnel=3.24
stunnel=3.25
stunnel=3.26
stunnel=4.00
stunnel=4.0
stunnel=4.01
stunnel=4.02
stunnel=4.03
stunnel=4.04
stunnel=4.05
stunnel=4.06
stunnel=4.07
stunnel=4.08
stunnel=4.09
stunnel=4.10
stunnel=4.11
stunnel=4.12
stunnel=4.13
stunnel=4.14
stunnel=4.15
stunnel=4.16
stunnel=4.17
stunnel=4.18
stunnel=4.19
stunnel=4.20
stunnel=4.21
stunnel=4.22
stunnel=4.23
stunnel=4.24
stunnel=4.25
stunnel=4.26
stunnel=4.27
stunnel=4.28
stunnel=4.29
stunnel=4.30
stunnel=4.31
stunnel=4.32
stunnel=4.33
stunnel=4.34
stunnel=4.35
stunnel=4.36
stunnel=4.37
stunnel=4.38
stunnel=4.39
stunnel=4.40
stunnel=4.41
stunnel=4.42
stunnel=4.43
stunnel=4.44
stunnel=4.45
stunnel=4.46
stunnel=4.47
stunnel=4.48
stunnel=4.49
stunnel=4.50
stunnel=4.51
stunnel=4.52
stunnel=4.53
stunnel=4.54
stunnel=4.55
<=4.56
=0.1
=1.0
=1.1
=1.2
=1.3
=1.4
=1.5
=1.6
=2.0
=2.1
=3.0
=3.0-b1
=3.0-b2
=3.0-b3
=3.0-b4
=3.0-b5
=3.0-b6
=3.0-b7
=3.1
=3.2
=3.3
=3.4a
=3.5
=3.6
=3.7
=3.8
=3.8-p1
=3.8-p2
=3.8-p3
=3.8-p4
=3.8p1
=3.8p2
=3.8p3
=3.8p4
=3.9
=3.10
=3.11
=3.12
=3.13
=3.14
=3.15
=3.16
=3.17
=3.18
=3.19
=3.20
=3.21
=3.21a
=3.21b
=3.21c
=3.22
=3.23
=3.24
=3.25
=3.26
=4.00
=4.0
=4.01
=4.02
=4.03
=4.04
=4.05
=4.06
=4.07
=4.08
=4.09
=4.10
=4.11
=4.12
=4.13
=4.14
=4.15
=4.16
=4.17
=4.18
=4.19
=4.20
=4.21
=4.22
=4.23
=4.24
=4.25
=4.26
=4.27
=4.28
=4.29
=4.30
=4.31
=4.32
=4.33
=4.34
=4.35
=4.36
=4.37
=4.38
=4.39
=4.40
=4.41
=4.42
=4.43
=4.44
=4.45
=4.46
=4.47
=4.48
=4.49
=4.50
=4.51
=4.52
=4.53
=4.54
=4.55

Remedy

https://bugzilla.redhat.com/attachment.cgi?id=870826&action=diff

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2014-0016?

    CVE-2014-0016 is considered a critical severity vulnerability due to improper random number generation after a fork, which can lead to predictable SSL keys.

  • How do I fix CVE-2014-0016?

    To fix CVE-2014-0016, it is recommended to upgrade to a fixed version of stunnel software that has addressed this vulnerability.

  • Which versions of stunnel are affected by CVE-2014-0016?

    CVE-2014-0016 affects stunnel versions up to 4.55 and certain versions from 0.1 to 3.23.

  • What is the impact of exploiting CVE-2014-0016?

    Exploiting CVE-2014-0016 can lead to compromised SSL communications due to predictable encryption keys.

  • Is there a known exploit for CVE-2014-0016?

    There have been reports of exploits leveraging CVE-2014-0016 to compromise SSL connections, making immediate remediation important.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203