Redis is an in-memory data structure store. In versions of redis-server up to 8.6.3, the RESTORE command does not properly validate serialized values. An authenticated attacker with permission to execute RESTORE can supply a crafted serialized payload that triggers invalid memory access and may lead to remote code execution. A workaround is to restrict access to the RESTORE command with ACL rules. This is patched in version 8.6.3.
Weakness
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Redis | Redis | * | 8.6.3 (excluding) |
| Red Hat Enterprise Linux 10 | RedHat | valkey-0:8.0.9-1.el10_2 | * |
| Red Hat Enterprise Linux 10.0 Extended Update Support | RedHat | valkey-0:8.0.9-1.el10_0 | * |
| Red Hat Enterprise Linux 8 | RedHat | redis:6-8100020260522105353.489197e6 | * |
| Red Hat Enterprise Linux 9 | RedHat | redis-0:6.2.22-1.el9_8 | * |
| Red Hat Enterprise Linux 9 | RedHat | redis:7-9080020260521083756.9 | * |
| Red Hat Enterprise Linux 9 | RedHat | valkey-0:8.0.9-1.el9_8 | * |
| Red Hat Enterprise Linux 9.6 Extended Update Support | RedHat | redis-0:6.2.22-1.el9_6 | * |
| Red Hat Enterprise Linux 9.6 Extended Update Support | RedHat | redis:7-9060020260602115714.9 | * |
| Redis | Ubuntu | esm-apps/xenial | * |
Potential Mitigations
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
- D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
- Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
- For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].