Microsoft security update for CVE-2024-12797
🔗 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-12797. This page also shows what EchelonGraph holds for CVE-2024-12797, 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 cloud-hypervisor-cvm 38.0.72.2-3 on Azure Linux 3.0
- azl3 cloud-hypervisor-cvm 41.0.79-3 on Azure Linux 3.0
- azl3 openssl 3.3.2-2 on Azure Linux 3.0
- azl3 openssl 3.3.3-1 on Azure Linux 3.0
- cbl2 cloud-hypervisor-cvm 38.0.72.2-5 on CBL Mariner 2.0
- cbl2 cloud-hypervisor-cvm 38.0.72.2-5 on CBL-Mariner 2.0
✅ Updates Microsoft lists: 3 updates
3 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 | 38.0.72.2-3 |
| — | Security Update | 38.0.72.2-5 |
🧭 EchelonGraph on CVE-2024-12797
- EchelonGraph score
- 6.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: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set. Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients. RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server's RPK fails to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER. Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2. The FIPS modules in 3.4, 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-12797, 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).