Integer overflow in certain command arguments can drive Redis to OOM panic
25Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.5epss 37%
exploitation probability
37%top 2% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected products
redis · redisReferences
https://github.com/redis/redis/commit/1ec82e6e97e1db06a72ca505f9fbf6b981f31ef7https://github.com/redis/redis/releases/tag/6.0.17https://github.com/redis/redis/releases/tag/6.2.9https://github.com/redis/redis/releases/tag/7.0.8https://github.com/redis/redis/security/advisories/GHSA-mrcw-fhw9-fj8jhttps://lists.debian.org/debian-lts-announce/2024/11/msg00031.html