CVE-2019-1549MediumMicrosoft CVSS 5.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Microsoft advisory for CVE-2019-1549

Published
April 26, 2026
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2019-1549 →

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2019-1549. This page also shows what EchelonGraph holds for CVE-2019-1549, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products16

  • azl3 rust 1.75.0-27 on Azure Linux 3.0
  • azl3 rust 1.75.0-28 on Azure Linux 3.0
  • azl3 rust 1.90.0-6 on Azure Linux 3.0
  • azl3 rust 1.90.0-7 on Azure Linux 3.0
  • azl3 shim-unsigned-aarch64 16.1-1 on Azure Linux 3.0
  • azl3 shim-unsigned-aarch64 16.1-2 on Azure Linux 3.0
  • azl3 shim-unsigned-x64 16.1-1 on Azure Linux 3.0
  • azl3 shim-unsigned-x64 16.1-2 on Azure Linux 3.0
  • cbl2 cloud-hypervisor 32.0-7 on CBL Mariner 2.0
  • cbl2 edk2 20230301gitf80f052277c8-47 on CBL Mariner 2.0
  • cbl2 hvloader 1.0.1-18 on CBL Mariner 2.0
  • cbl2 openssl 1.1.1k-39 on CBL Mariner 2.0
  • cbl2 qemu 6.2.0-27 on CBL Mariner 2.0
  • cbl2 rust 1.72.0-15 on CBL Mariner 2.0
  • cbl2 shim-unsigned-aarch64 15-5 on CBL Mariner 2.0
  • cbl2 shim-unsigned-x64 15.8-1 on CBL Mariner 2.0

🧭 EchelonGraph on CVE-2019-1549

EchelonGraph score
5.3 MEDIUM
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

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

Published by OpenSSL Software Foundation, the CVE Numbering Authority that assigned CVE-2019-1549, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (1)