Microsoft security update for CVE-2024-9143
🔗 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-2024-9143. This page also shows what EchelonGraph holds for CVE-2024-9143, 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 products12
- azl3 cloud-hypervisor 41.0.139-1 on Azure Linux 3.0
- azl3 cloud-hypervisor-cvm 41.0.79-1 on Azure Linux 3.0
- azl3 edk2 20240524git3e722403cd16-8 on Azure Linux 3.0
- azl3 openssl 3.3.2-2 on Azure Linux 3.0
- azl3 qemu 8.2.0-16 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-cvm 38.0.72.2-5 on CBL Mariner 2.0
- cbl2 hvloader 1.0.1-5 on CBL Mariner 2.0
- cbl2 openssl 1.1.1k-36 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
✅ Updates Microsoft lists: 2 updates
2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 3.3.3-1 |
| — | Security Update | 1.0.1-6 |
🧭 EchelonGraph on CVE-2024-9143
- EchelonGraph score
- 4.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
Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes. Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low. In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding. The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions. Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Published by OpenSSL Software Foundation, the CVE Numbering Authority that assigned CVE-2024-9143, 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).