CVE-2014-0016: stunnel before 5.00, when using fork threading, does not properly update the state of the OpenSSL pseudo-rando

Q: How do I fix CVE-2014-0016?

stunnel: upgrade to newer than 4.56. Exact commands for each OS are on this page.

Q: Is CVE-2014-0016 being exploited?

CVE-2014-0016 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2014-0016 affect?

CVE-2014-0016 affects stunnel. Severity is medium (CVSS 4.3). stunnel before 5.00, when using fork threading, does not properly update the state of the OpenSSL pseudo-random number generator (PRNG), which causes subsequent children with the same process ID to use the same entropy pool and allows remot

Q: How urgent is CVE-2014-0016?

Priority 41/100. On your watchlist

This month

MEDIUM 4.3WATCHLISTUPGRADE

CVE-2014-0016 is a medium-severity flaw (CVSS 4.3) affecting stunnel. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

stunnel before 5.00, when using fork threading, does not properly update the state of the OpenSSL pseudo-random number generator (PRNG), which causes subsequent children with the same process ID to use the same entropy pool and allows remote attackers to obtain private keys for EC (ECDSA) or DSA certificates.

Why this priority

On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
EPSS exploit chance	2.2% (top 18%)
CISA exploited list	No
Weakness	CWE-332
Published	2014-03-24
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: stunnel

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2014-03-24 16:31 UTCPublished CVE record published
2026-06-17 00:02 UTCUpdated Record last modified

stunnel stunnel UPGRADE

Affected: <= 4.56 · 0.1 · 1.0 · 1.1 · 1.2 · 1.3 · 1.4 · 1.5

Fixed in: newer than 4.56

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy stunnel || rpm -q stunnel || stunnel --version

2. UPGRADE to newer than 4.56 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade stunnel

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade stunnel

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2014-0016?

stunnel: upgrade to newer than 4.56. Exact commands for each OS are on this page.

Is CVE-2014-0016 being exploited?

CVE-2014-0016 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2014-0016 affect?

CVE-2014-0016 affects stunnel. Severity is medium (CVSS 4.3). stunnel before 5.00, when using fork threading, does not properly update the state of the OpenSSL pseudo-random number generator (PRNG), which causes subsequent children with the same process ID to use the same entropy pool and allows remot

How urgent is CVE-2014-0016?

Priority 41/100. On your watchlist

Software pages

OpenSSL vulnerabilities

Related CVEs

CVE-2021-20230 HIGH 7.5 UPGRADE A flaw was found in stunnel before 5.57, where it improperly validates client certificates when it is configur
CVE-2015-3644 MEDIUM 5.8 DOWNGRADE Stunnel 5.00 through 5.13, when using the redirect option, does not redirect client connections to the expecte
CVE-2013-1762 MEDIUM 6.6 UPGRADE stunnel 4.21 through 4.54, when CONNECT protocol negotiation and NTLM authentication are enabled, does not cor
CVE-2011-2940 HIGH 9.3 DOWNGRADE stunnel 4.40 and 4.41 might allow remote attackers to execute arbitrary code or cause a denial of service (hea

References

← Back to latest CVEs