Microsoft security update for CVE-2023-39533
🔗 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-2023-39533. This page also shows what EchelonGraph holds for CVE-2023-39533, 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 products7
- azl3 golang 1.19.12-1 on Azure Linux 3.0
- azl3 golang 1.27.0-1 on Azure Linux 3.0
- cbl2 golang 1.17.13-2 on CBL Mariner 2.0
- cbl2 golang 1.18.8-7 on CBL Mariner 2.0
- cbl2 golang 1.19.12-1 on CBL Mariner 2.0
- cbl2 golang 1.21.6-1 on CBL Mariner 2.0
- cbl2 msft-golang 1.19.12-1 on CBL Mariner 2.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 | — |
| — | Security Update | 1.21.6-1 |
| — | Security Update | 1.19.12-1 |
| — | Security Update | — |
🧭 EchelonGraph on CVE-2023-39533
- 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
go-libp2p is the Go implementation of the libp2p Networking Stack. Prior to versions 0.27.8, 0.28.2, and 0.29.1 malicious peer can use large RSA keys to run a resource exhaustion attack & force a node to spend time doing signature verification of the large key. This vulnerability is present in the core/crypto module of go-libp2p and can occur during the Noise handshake and the libp2p x509 extension verification step. To prevent this attack, go-libp2p versions 0.27.8, 0.28.2, and 0.29.1 restrict RSA keys to <= 8192 bits. To protect one's application, it is necessary to update to these patch releases and to use the updated Go compiler in 1.20.7 or 1.19.12. There are no known workarounds for this issue.
Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2023-39533, 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).