Yossigopublished

**Name of the Vulnerable Software and Affected Versions** Redis versions prior to 7.0.15 Redis versions prior to 7.2.4 **Description** The issue is related to integer overflow due to incorrect handling of memory buffer resizing, which can lead to heap overflow and potential remote code execution. The estimated number of potentially affected devices worldwide is over 1.4 million, mainly distributed in China, the United States, and other countries. **Recommendations** For versions prior to 7.0.15, update to version 7.0.15 or later. For versions prior to 7.2.4, update to version 7.2.4 or later.

**Name of the Vulnerable Software and Affected Versions** Redis versions 7.0.0 through 7.0.3 **Description** The issue is related to a heap overflow that can potentially lead to remote code execution. This occurs when a specially crafted `XAUTOCLAIM` command is executed on a stream key in a specific state. **Recommendations** For versions 7.0.0 through 7.0.3, update to version 7.0.4 to resolve the issue. As a temporary workaround, consider restricting the use of the `XAUTOCLAIM` command on stream keys until the patch is applied.

**Name of the Vulnerable Software and Affected Versions** Redis versions 2.2 through 5.0.12 Redis versions 6.0 through 6.0.14 Redis versions 6.2 through 6.2.4 **Description** A vulnerability involving out-of-bounds read and integer overflow to buffer overflow exists in Redis. The vulnerability can be exploited to corrupt the heap, leak arbitrary heap contents, or trigger remote code execution. This issue affects Redis on 32-bit platforms or compiled as a 32-bit binary. The vulnerability involves changing the default `proto-max-bulk-len` configuration parameter to a very large value and constructing specially crafted commands. **Recommendations** For Redis versions 2.2 through 5.0.12, update to version 5.0.13 or later. For Redis versions 6.0 through 6.0.14, update to version 6.0.15 or later. For Redis versions 6.2 through 6.2.4, update to version 6.2.5 or later. As a temporary workaround, prevent users from modifying the `proto-max-bulk-len` configuration parameter by using ACL to restrict unprivileged users from using the CONFIG SET command.