Use of Insufficiently Random Values Affecting openssl11-devel package, versions <1:1.1.1c-15.amzn2.0.1


Severity

Recommended
0.0
medium
0
10

Based on Amazon Linux security rating

    Threat Intelligence

    EPSS
    1.14% (85th 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 ID SNYK-AMZN2-OPENSSL11DEVEL-1681115
  • published 27 Sep 2021
  • disclosed 10 Sep 2019

How to fix?

Upgrade Amazon-Linux:2 openssl11-devel to version 1:1.1.1c-15.amzn2.0.1 or higher.
This issue was patched in ALAS2-2020-1456.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl11-devel package and not the openssl11-devel package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2 relevant fixed versions and status.

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
Expand this section

NVD

5.3 medium
  • Attack Vector (AV)
    Network
  • Attack Complexity (AC)
    Low
  • Privileges Required (PR)
    None
  • User Interaction (UI)
    None
  • Scope (S)
    Unchanged
  • Confidentiality (C)
    Low
  • Integrity (I)
    None
  • Availability (A)
    None