Redis is an in-memory database that persists on disk. Authenticated users issuing specially crafted `SETRANGE` and `SORT(_RO)` commands can trigger an integer overflow, resulting with Redis attempting to allocate impossible amounts of memory and abort with an out-of-memory (OOM) panic. The problem is fixed in Redis versions 7.0.8, 6.2.9 and 6.0.17. Users are advised to upgrade. There are no known workarounds for this vulnerability.
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
| Link | Tags |
|---|---|
| https://github.com/redis/redis/security/advisories/GHSA-mrcw-fhw9-fj8j | third party advisory |
| https://github.com/redis/redis/commit/1ec82e6e97e1db06a72ca505f9fbf6b981f31ef7 | third party advisory patch |
| https://github.com/redis/redis/releases/tag/6.0.17 | third party advisory release notes |
| https://github.com/redis/redis/releases/tag/6.2.9 | third party advisory release notes |
| https://github.com/redis/redis/releases/tag/7.0.8 | third party advisory release notes |