Microsoft security update for CVE-2024-13176
🔗 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-13176. This page also shows what EchelonGraph holds for CVE-2024-13176, 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 20240524git3e722403cd16-6 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 openssl 3.3.3-1 on Azure Linux 3.0
- cbl2 openssl 1.1.1k-36 on CBL Mariner 2.0
- cbl2 openssl 1.1.1k-36 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 | 20240524git3e722403cd16-6 |
| — | Security Update | 3.3.3-1 |
| — | Security Update | 1.1.1k-36 |
🧭 EchelonGraph on CVE-2024-13176
- EchelonGraph score
- 4.1 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: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation. Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency. There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low. The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are affected by this issue.
Published by OpenSSL Software Foundation, the CVE Numbering Authority that assigned CVE-2024-13176, 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).