Skip to content

go-redis allows potential out of order responses when `CLIENT SETINFO` times out during connection establishment

Low severity GitHub Reviewed Published Mar 20, 2025 in redis/go-redis • Updated Mar 20, 2025

Package

gomod github.com/redis/go-redis/v9 (Go)

Affected versions

>= 9.7.0-beta.1, < 9.7.3
>= 9.6.0b1, < 9.6.3
>= 9.5.1, < 9.5.5

Patched versions

9.7.3
9.6.3
9.5.5

Description

Impact

The issue only occurs when the CLIENT SETINFO command times out during connection establishment. The following circumstances can cause such a timeout:

  1. The client is configured to transmit its identity. This can be disabled via the DisableIndentity flag.
  2. There are network connectivity issues
  3. The client was configured with aggressive timeouts

The impact differs by use case:

  • Sticky connections: Rather than using a connection from the pool on-demand, the caller can stick with a connection. Then you receive persistent out-of-order responses for the lifetime of the connection.
  • Pipelines: All commands in the pipeline receive incorrect responses.
  • Default connection pool usage without pipelining: 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.

Patches

We prepared a fix in redis/go-redis#3295 and plan to release patch versions soon.

Workarounds

You can prevent the vulnerability by setting the flag DisableIndentity (BTW: We also need to fix the spelling.) to true when constructing the client instance.

Credit

Akhass Wasti
Ramin Ghorashi
Anton Amlinger
Syed Rahman
Mahesh Venkateswaran
Sergey Zavoloka
Aditya Adarwal
Abdulla Anam
Abd-Alhameed
Alex Vanlint
Gaurav Choudhary
Vedanta Jha
Yll Kelani
Ryan Picard

References

@dmaier-redislabs dmaier-redislabs published to redis/go-redis Mar 20, 2025
Published by the National Vulnerability Database Mar 20, 2025
Published to the GitHub Advisory Database Mar 20, 2025
Reviewed Mar 20, 2025
Last updated Mar 20, 2025

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(11th percentile)

Weaknesses

CVE ID

CVE-2025-29923

GHSA ID

GHSA-92cp-5422-2mw7

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.