Insecure Randomness Affecting openssl package, versions [1.1.1,1.1.1d)


Severity

Recommended
0.0
medium
0
10

CVSS assessment made by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
2.86% (91st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-UNMANAGED-OPENSSL-2318619
  • published14 Dec 2021
  • disclosed10 Sept 2019
  • creditUnknown

Introduced: 10 Sep 2019

CVE-2019-1549  (opens in a new tab)
CWE-330  (opens in a new tab)

How to fix?

Upgrade openssl to version 1.1.1d or higher.

Overview

Affected versions of this package are vulnerable to Insecure Randomness. OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

References

CVSS Scores

version 3.1