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).
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: openssl

Published: 2019-09-10T16:58:35.361288Z

Updated: 2024-09-16T22:56:57.501Z

Reserved: 2018-11-28T00:00:00

Link: CVE-2019-1549

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2019-09-10T17:15:11.813

Modified: 2024-11-21T04:36:48.343

Link: CVE-2019-1549

cve-icon Redhat

Severity : Low

Publid Date: 2019-09-10T00:00:00Z

Links: CVE-2019-1549 - Bugzilla