QID 355142

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. (
( CVE-2022-35977) redis is an in-memory database that persists on disk.
Authenticated users can use string matching commands (like `scan` or `keys`) with a specially crafted pattern to trigger a denial-of-service attack on redis, causing it to hang and consume 100% cpu time.
The problem is fixed in redis versions 6.0.18, 6.2.11, 7.0.9. (
( CVE-2022-36021) ** disputed ** a vulnerability, which was classified as problematic, was found in redis.
Affected is the function sigsegvhandler of the file debug.c of the component crash report.
The manipulation leads to denial of service.
The real existence of this vulnerability is still doubted at the moment.
The name of the patch is 0bf90d944313919eb8e63d3588bf63a367f020a3.
It is recommended to apply a patch to fix this issue.
Vdb-211962 is the identifier assigned to this vulnerability.
Note: the vendor claims that this is not a dos because it applies to the crash logging mechanism which is triggered after a crash has occurred. (
( CVE-2022-3647) redis is an in-memory database that persists on disk.
This problem affects all redis versions.
Patches were released in redis version(s) 6.0.18, 6.2.11 and 7.0.9. (

Successful exploitation of this vulnerability could lead to a securitybreach or could affect integrity, availability, and confidentiality.