CVE Vulnerabilities

CVE-2019-10192

Heap-based Buffer Overflow

Published: Jul 11, 2019 | Modified: Nov 21, 2024
CVSS 3.x
7.2
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
6.5 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P
RedHat/V2
RedHat/V3
7.2 IMPORTANT
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

A heap-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 carefully corrupting a hyperloglog using the SETRANGE command, an attacker could trick Redis interpretation of dense HLL encoding to write up to 3 bytes beyond the end of a heap-allocated buffer.

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

NameVendorStart VersionEnd Version
RedisRedislabs3.0.0 (including)3.2.13 (excluding)
RedisRedislabs4.0.0 (including)4.0.14 (excluding)
RedisRedislabs5.0 (including)5.0.4 (excluding)
Red Hat Enterprise Linux 8RedHatredis:5-8000020190711140130.f8e95b4e*
Red Hat OpenStack Platform 10.0 (Newton)RedHatredis-0:3.0.6-5.el7ost*
Red Hat OpenStack Platform 13.0 (Queens)RedHatredis-0:3.2.8-4.el7ost*
Red Hat OpenStack Platform 14.0 (Rocky)RedHatredis-0:3.2.8-4.el7ost*
Red Hat OpenStack Platform 9.0 (Mitaka)RedHatredis-0:3.0.6-5.el7ost*
Red Hat OpenStack Platform 9.0 Operational Tools for RHEL 7RedHatredis-0:3.0.6-5.el7ost*
Red Hat Software Collections for Red Hat Enterprise Linux 6RedHatrh-redis32-redis-0:3.2.13-1.el6*
Red Hat Software Collections for Red Hat Enterprise Linux 7RedHatrh-redis5-redis-0:5.0.5-1.el7*
Red Hat Software Collections for Red Hat Enterprise Linux 7RedHatrh-redis32-redis-0:3.2.13-1.el7*
Red Hat Software Collections for Red Hat Enterprise Linux 7.4 EUSRedHatrh-redis5-redis-0:5.0.5-1.el7*
Red Hat Software Collections for Red Hat Enterprise Linux 7.4 EUSRedHatrh-redis32-redis-0:3.2.13-1.el7*
Red Hat Software Collections for Red Hat Enterprise Linux 7.5 EUSRedHatrh-redis5-redis-0:5.0.5-1.el7*
Red Hat Software Collections for Red Hat Enterprise Linux 7.5 EUSRedHatrh-redis32-redis-0:3.2.13-1.el7*
Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUSRedHatrh-redis5-redis-0:5.0.5-1.el7*
Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUSRedHatrh-redis32-redis-0:3.2.13-1.el7*
RedisUbuntubionic*
RedisUbuntucosmic*
RedisUbuntudisco*
RedisUbuntuesm-apps/bionic*
RedisUbuntuesm-apps/xenial*
RedisUbuntutrusty*
RedisUbuntuupstream*
RedisUbuntuxenial*

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