CVE-2019-1549Not scoredCWE-330

CVE-2019-1549: Fork Protection

OpenSSL

Vendor fix available · Affected: OpenSSL · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

6.2%probability of exploitation in the next 30 days

93rd percentile

050100

Higher than 93% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

OpenSSL · OpenSSLFixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c)

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Use of Insufficiently Random Values · Cryptography
Vendor: OpenSSL
Published: September 2019
Band: Possible (1 to 10%), September 2019

CoverageNo articles yet

No CyberSIXT article names CVE-2019-1549 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

3 more references are in the CVE record.