Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

debian логотип

CVE-2021-3470

Опубликовано: 31 мар. 2021
Источник: debian

Описание

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.

Пакеты

ПакетСтатусВерсия исправленияРелизТип
redisfixed5:6.0.9-1package

Примечания

  • https://github.com/redis/redis/pull/7963

  • https://github.com/redis/redis/commit/9824fe3e392caa04dc1b4071886e9ac402dd6d95

  • Only an issue if not using a heap allocator other than jemalloc or glibc's malloc

Связанные уязвимости

CVSS3: 5.3
ubuntu
почти 5 лет назад

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.

CVSS3: 5.3
redhat
больше 5 лет назад

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.

CVSS3: 5.3
nvd
почти 5 лет назад

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.

CVSS3: 5.3
msrc
почти 5 лет назад

Описание отсутствует

github
больше 3 лет назад

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.