A stack-buffer overflow vulnerability was found in the Redis hyperloglog data structure versions 3.x before 3.2.13, 4.x before 4.0.14 and 5.x before 5.0.4. By corrupting a hyperloglog using the SETRANGE command, an attacker could cause Redis to perform controlled increments of up to 12 bytes past the end of a stack-allocated buffer.
Weakness
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Redis |
Redislabs |
3.0.0 (including) |
3.2.13 (excluding) |
| Redis |
Redislabs |
4.0.0 (including) |
4.0.14 (excluding) |
| Redis |
Redislabs |
5.0 (including) |
5.0.4 (excluding) |
| Red Hat Enterprise Linux 8 |
RedHat |
redis:5-8000020190711140130.f8e95b4e |
* |
| Red Hat Software Collections for Red Hat Enterprise Linux 7 |
RedHat |
rh-redis5-redis-0:5.0.5-1.el7 |
* |
| Red Hat Software Collections for Red Hat Enterprise Linux 7.4 EUS |
RedHat |
rh-redis5-redis-0:5.0.5-1.el7 |
* |
| Red Hat Software Collections for Red Hat Enterprise Linux 7.5 EUS |
RedHat |
rh-redis5-redis-0:5.0.5-1.el7 |
* |
| Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS |
RedHat |
rh-redis5-redis-0:5.0.5-1.el7 |
* |
| Redis |
Ubuntu |
disco |
* |
| Redis |
Ubuntu |
trusty |
* |
| Redis |
Ubuntu |
upstream |
* |
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].
References