Microsoft security update for CVE-2025-29923 — azl3
🔗 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-2025-29923. This page also shows what EchelonGraph holds for CVE-2025-29923, 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 products12
- azl3 keda 2.14.1-5 on Azure Linux 3.0
- azl3 keda 2.14.1-7 on Azure Linux 3.0
- azl3 telegraf 1.31.0-10 on Azure Linux 3.0
- azl3 telegraf 1.31.0-11 on Azure Linux 3.0
- azl3 telegraf 1.31.0-12 on Azure Linux 3.0
- azl3 telegraf 1.31.0-15 on Azure Linux 3.0
- azl3 telegraf 1.31.0-17 on Azure Linux 3.0
- azl3 telegraf 1.31.0-19 on Azure Linux 3.0
- azl3 telegraf 1.31.0-22 on Azure Linux 3.0
- azl3 telegraf 1.31.0-23 on Azure Linux 3.0
- azl3 telegraf 1.31.0-27 on Azure Linux 3.0
- azl3 telegraf 1.31.0-28 on Azure Linux 3.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 | 1.31.0-24 |
| — | Security Update | 2.14.1-5 |
| — | Security Update | 1.31.0-27 |
🧭 EchelonGraph on CVE-2025-29923
- EchelonGraph score
- 3.7 LOW
- 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-redis is the official Redis client library for the Go programming language. Prior to 9.5.5, 9.6.3, and 9.7.2, go-redis potentially responds out of order when `CLIENT SETINFO` times out during connection establishment. This can happen when the client is configured to transmit its identity, there are network connectivity issues, or the client was configured with aggressive timeouts. The problem occurs for multiple use cases. For sticky connections, you receive persistent out-of-order responses for the lifetime of the connection. All commands in the pipeline receive incorrect responses. When used with the default ConnPool once a connection is returned after use with ConnPool#Put the read buffer will be checked and the connection will be marked as bad due to the unread data. This means that at most one out-of-order response before the connection is discarded. This issue is fixed in 9.5.5, 9.6.3, and 9.7.2; however, 9.7.2 has been yanked and 9.7.3 is the lowest available patched version on the 9.7.x branch. As a workaround, set the flag `DisableIndentity` to `true` when constructing the client instance.
Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2025-29923, 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).