Microsoft advisory for CVE-2019-1547
🔗 CVE IDs covered (1)
📋 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-1547. This page also shows what EchelonGraph holds for CVE-2019-1547, 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 products11
- 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 15.8-5 on Azure Linux 3.0
- azl3 shim-unsigned-x64 15.8-5 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 rust 1.72.0-15 on CBL Mariner 2.0
🧭 EchelonGraph on CVE-2019-1547
- EchelonGraph score
- 4.7 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
Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).
Published by OpenSSL Software Foundation, the CVE Numbering Authority that assigned CVE-2019-1547, 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).