CVE-2019-1549
MEDIUMEPSS 93th pctlDescription
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).
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Exploit Intelligence
High risk: more likely to be exploited than 93% of all known CVEs.
References
Related Vulnerabilities
Other CWE-330 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-5420 | Critical | 9.8 | 92% | - | Fix |
| CVE-2021-34646 | Critical | 9.8 | 51% | - | - |
| CVE-2008-0087 | High | 7.5 | 32% | - | - |
| CVE-2017-6026 | Critical | 9.1 | 32% | - | - |
| CVE-2018-17888 | Critical | 9.8 | 30% | - | - |
| CVE-2020-11901 | Critical | 9.0 | 21% | - | Fix |
Common questions
How do I fix CVE-2019-1549?
Published advisories record a fix for 4 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2019-1549 being actively exploited?
Not that we know of. CVE-2019-1549 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 6.2% is the estimated probability that it will be exploited in the next 30 days. That is higher than 93% of all scored CVEs.
How severe is CVE-2019-1549?
CVE-2019-1549 has a CVSS v3 base score of 5.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2019-1549 affect?
Published advisories record a fix for openssl (Debian), libssl1.0.0 (Ubuntu), libssl1.1 (Ubuntu), openssl (Ubuntu). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2019-1549
Markdown
[](https://tridentstack.com/cve/CVE-2019-1549)HTML
<a href="https://tridentstack.com/cve/CVE-2019-1549"><img src="https://tridentstack.com/cve/badge/CVE-2019-1549.svg" alt="CVE-2019-1549"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.