Bug 2353925 (CVE-2025-29923)

Summary:	CVE-2025-29923 github.com/redis/go-redis: go-redis allows potential out of order responses when `CLIENT SETINFO` times out during connection establishment
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security DevOps Team <prodsec-dev>
Status:	NEW ---	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	aazores, abarbaro, adistefa, ahrabovs, alcohan, amctagga, anjoseph, aoconnor, aucunnin, bniver, cmah, dbosanac, dhanak, drosa, dsimansk, eaguilar, ebaron, flucifre, gmeno, gparvin, jcantril, jchui, jhe, jolong, jprabhak, jreimann, jsherril, kaycoth, kingland, ktsao, kverlaen, lball, lchilton, matzew, mbenjamin, mdessi, mhackett, mnovotny, mrizzi, mstoklus, nboldt, ngough, njean, oezr, owatkins, pahickey, pcattana, periklis, pjindal, psrna, rhaigner, rojacob, sausingh, sdawley, sfeifer, sostapov, vereddy, veshanka, wtam
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in go-redis. This vulnerability allows out-of-order responses and incorrect command execution via CLIENT SETINFO timeouts during connection establishment, potentially leading to data inconsistency.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2025-03-20 19:01:17 UTC

go-redis is the official Redis client library for the Go programming language. Prior to 9.5.5, 9.6.3, and 9.7.3, 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.3. You can prevent the vulnerability by setting the flag DisableIndentity to true when constructing the client instance.