ID CVE-2021-32762
Summary Redis is an open source, in-memory database that persists on disk. The redis-cli command line tool and redis-sentinel service may be vulnerable to integer overflow when parsing specially crafted large multi-bulk network replies. This is a result of a vulnerability in the underlying hiredis library which does not perform an overflow check before calling the calloc() heap allocation function. This issue only impacts systems with heap allocators that do not perform their own overflow checks. Most modern systems do and are therefore not likely to be affected. Furthermore, by default redis-sentinel uses the jemalloc allocator which is also not vulnerable. The problem is fixed in Redis versions 6.2.6, 6.0.16 and 5.0.14.
References
Vulnerable Configurations
  • cpe:2.3:a:redis:redis:6.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.10:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.10:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.11:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.11:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.12:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.12:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.13:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.13:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.14:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.14:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:6.0.15:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:6.0.15:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:5.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:5.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:5.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:5.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:5.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:5.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:5.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:5.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:5.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:5.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:5.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:5.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:5.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:5.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:5.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:5.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:5.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:5.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:5.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:5.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:5.0.10:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:5.0.10:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:5.0.11:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:5.0.11:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:5.0.12:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:5.0.12:*:*:*:*:*:*:*
  • cpe:2.3:a:redis:redis:5.0.13:*:*:*:*:*:*:*
    cpe:2.3:a:redis:redis:5.0.13:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
  • cpe:2.3:o:fedoraproject:fedora:33:*:*:*:*:*:*:*
    cpe:2.3:o:fedoraproject:fedora:33:*:*:*:*:*:*:*
  • cpe:2.3:o:fedoraproject:fedora:34:*:*:*:*:*:*:*
    cpe:2.3:o:fedoraproject:fedora:34:*:*:*:*:*:*:*
  • cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*
    cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*
  • cpe:2.3:a:netapp:management_services_for_element_software:-:*:*:*:*:*:*:*
    cpe:2.3:a:netapp:management_services_for_element_software:-:*:*:*:*:*:*:*
  • cpe:2.3:a:netapp:management_services_for_netapp_hci:-:*:*:*:*:*:*:*
    cpe:2.3:a:netapp:management_services_for_netapp_hci:-:*:*:*:*:*:*:*
  • cpe:2.3:a:oracle:communications_operations_monitor:4.3:*:*:*:*:*:*:*
    cpe:2.3:a:oracle:communications_operations_monitor:4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:oracle:communications_operations_monitor:4.4:*:*:*:*:*:*:*
    cpe:2.3:a:oracle:communications_operations_monitor:4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:oracle:communications_operations_monitor:5.0:*:*:*:*:*:*:*
    cpe:2.3:a:oracle:communications_operations_monitor:5.0:*:*:*:*:*:*:*
CVSS
Base: 9.0 (as of 13-05-2022 - 17:21)
Impact:
Exploitability:
CWE CWE-680
CAPEC
  • Overflow Variables and Tags
    This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • String Format Overflow in syslog()
    This attack targets the format string vulnerabilities in the syslog() function. An attacker would typically inject malicious input in the format string parameter of the syslog function. This is a common problem, and many public vulnerabilities and associated exploits have been posted.
  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Filter Failure through Buffer Overflow
    In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
  • Client-side Injection-induced Buffer Overflow
    This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an adversary. As a consequence, an adversary is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the adversaries' choice.
  • Forced Integer Overflow
    This attack forces an integer variable to go out of range. The integer variable is often used as an offset such as size of memory allocation or similarly. The attacker would typically control the value of such variable and try to get it out of range. For instance the integer in question is incremented past the maximum possible value, it may wrap to become a very small, or negative number, therefore providing a very incorrect value which can lead to unexpected behavior. At worst the attacker can execute arbitrary code.
Access
VectorComplexityAuthentication
NETWORK LOW SINGLE
Impact
ConfidentialityIntegrityAvailability
COMPLETE COMPLETE COMPLETE
cvss-vector via4 AV:N/AC:L/Au:S/C:C/I:C/A:C
Last major update 13-05-2022 - 17:21
Published 04-10-2021 - 18:15
Last modified 13-05-2022 - 17:21
Back to Top