CVE-2014-0016

Public on

Last Modified: UTC

Description

The CVE Program describes this issue as:

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.

Statement

Not vulnerable. This issue does not affect the version of stunnel package as shipped with Red Hat Enterprise Linux 5 and 6.

Not vulnerable. This issue does not affect the version of stunnel package as shipped with Red Hat Enterprise Linux 5 and 6.

Additional information

  • Bugzilla 1072180: stunnel: Improper initialization of PRNG after fork()
  • FAQ: Frequently asked questions about CVE-2014-0016

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v2 Score Breakdown
Red HatNVD

CVSS v2 Base Score

4.3

4.3

Attack Vector

Network

Network

Access Complexity

Medium

Medium

Authentication

None

None

Confidentiality Impact

Partial

Partial

Integrity Impact

None

None

Availability Impact

None

None

CVSS v2 Vector

Red Hat: AV:N/AC:M/Au:N/C:P/I:N/A:N

NVD: AV:N/AC:M/Au:N/C:P/I:N/A:N

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?

What can I do if my product is listed as "Will not fix"?

What can I do if my product is listed as "Fix deferred"?

What is a mitigation?

I have a Red Hat product but it is not in the above list, is it affected?

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

Want to get errata notifications? Sign up here.