Loading vulnerability…
CVE-2019-1549 is an information-disclosure vulnerability in the random number generator rewritten for OpenSSL 1.1.1. The RNG was intended to register fork() protection so that child processes reseed and do not retain the parent process's RNG state. In the default initialization path, this protection was not enabled. Consequently, a parent and child process created through fork() could retain shared RNG state and potentially produce the same random output. High-precision timer input is mixed into RNG state and substantially reduces the probability of state duplication, but does not provide complete fork protection. Applications explicitly initializing libcrypto with OPENSSL_INIT_ATFORK are not affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Security vulnerability addressed by the advisory; no technical details are provided.
An information-disclosure vulnerability in OpenSSL related to fork() processing.
An OpenSSL information-disclosure vulnerability involving fork().
An OpenSSL information-disclosure vulnerability involving fork(); addressed by Red Hat's OpenSSL update RHSA-2020:1840.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.