First published: Fri Mar 26 2021(Updated: )
A heap overflow issue was found in Redis in versions before 5.0.10, before 6.0.9 and before 6.2.0 when using a heap allocator other than jemalloc or glibc's malloc, leading to potential out of bound write or process crash. Effectively this flaw does not affect the vast majority of users, who use jemalloc or glibc malloc.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Redislabs Redis | <5.0.10 | |
Redislabs Redis | >=6.0.0<6.0.9 | |
Redislabs Redis | =6.2.0-rc1 | |
Redislabs Redis | =6.2.0-rc2 | |
Redislabs Redis | =6.2.0-rc3 | |
redhat/redis | <5.0.10 | 5.0.10 |
redhat/redis | <6.0.9 | 6.0.9 |
redhat/redis | <6.2.0 | 6.2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-3470 is a heap overflow issue found in Redis in versions before 5.0.10, before 6.0.9, and before 6.2.0 when using a heap allocator other than jemalloc or glibc's malloc.
The severity of CVE-2021-3470 is medium with a severity value of 5.3.
Redis versions before 5.0.10, before 6.0.9, and before 6.2.0 are affected by CVE-2021-3470.
CVE-2021-3470 does not affect the vast majority of Redis users who use jemalloc as their heap allocator.
You can find more information about CVE-2021-3470 at the following link: https://bugzilla.redhat.com/show_bug.cgi?id=1943623