Microsoft security update for CVE-2023-31130
🔗 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-31130. This page also shows what EchelonGraph holds for CVE-2023-31130, 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 products9
- azl3 grpc 1.42.0-7 on Azure Linux 3.0
- azl3 grpc 1.62.0-2 on Azure Linux 3.0
- cbl2 c-ares 1.19.1-1 on CBL Mariner 2.0
- cbl2 fluent-bit 2.1.10-1 on CBL Mariner 2.0
- cbl2 grpc 1.42.0-11 on CBL Mariner 2.0
- cbl2 nodejs 16.20.1-2 on CBL Mariner 2.0
- cbl2 nodejs18 18.17.1-2 on CBL Mariner 2.0
- cbl2 python-gevent 21.1.2-3 on CBL Mariner 2.0
- cm1 c-ares 1.19.1-1 on CBL Mariner 1.0
✅ Updates Microsoft lists: 7 updates
7 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.19.1-1 |
| — | Security Update | 21.1.2-3 |
| — | Security Update | 18.17.1-2 |
| — | Security Update | 16.20.1-2 |
| — | Security Update | 1.42.0-11 |
| — | Security Update | 2.1.10-1 |
| — | Security Update | 1.62.0-2 |
🧭 EchelonGraph on CVE-2023-31130
- 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
c-ares is an asynchronous resolver library. ares_inet_net_pton() is vulnerable to a buffer underflow for certain ipv6 addresses, in particular "0::00:00:00/2" was found to cause an issue. C-ares only uses this function internally for configuration purposes which would require an administrator to configure such an address via ares_set_sortlist(). However, users may externally use ares_inet_net_pton() for other purposes and thus be vulnerable to more severe issues. This issue has been fixed in 1.19.1.
Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2023-31130, 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).