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
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: openssl
Published: 2019-09-10T00:00:00
Updated: 2020-10-20T21:14:59
Reserved: 2018-11-28T00:00:00
Link: CVE-2019-1549
JSON object: View
NVD Information
Status : Modified
Published: 2019-09-10T17:15:11.813
Modified: 2023-11-07T03:08:28.563
Link: CVE-2019-1549
JSON object: View
Redhat Information
No data.
CWE