Microsoft security update for CVE-2022-2097
🔗 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-2022-2097. This page also shows what EchelonGraph holds for CVE-2022-2097, 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 products6
- azl3 edk2 20230301gitf80f052277c8-37 on Azure Linux 3.0
- azl3 edk2 20240223gitedc6681206c1-1 on Azure Linux 3.0
- azl3 hvloader 1.0.1-1 on Azure Linux 3.0
- azl3 hvloader 1.0.1-2 on Azure Linux 3.0
- cbl2 openssl 1.1.1k-20 on CBL Mariner 2.0
- cm1 openssl 1.1.1k-12 on CBL Mariner 1.0
✅ Updates Microsoft lists: 4 updates
4 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 | 1.0.1-2 |
| — | Security Update | 20240223gitedc6681206c1-1 |
| — | Security Update | 1.1.1k-12 |
| — | Security Update | 1.1.1k-20 |
🧭 EchelonGraph on CVE-2022-2097
- EchelonGraph score
- 7.5 HIGH
- 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
AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p).
Published by OpenSSL Software Foundation, the CVE Numbering Authority that assigned CVE-2022-2097, 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).