CVE-2021-21309 Vulnerability Analysis & Exploit Details

CVE-2021-21309
Vulnerability Scoring

5.4
/10
Significant Risk

Security assessments indicate that CVE-2021-21309 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2021-21309 Details

Status: Modified

Last updated: 🕠 21 Nov 2024, 05:47 UTC
Originally published on: 🕙 26 Feb 2021, 22:15 UTC

Time between publication and last update: 1363 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:L

CVE-2021-21309 Vulnerability Summary

CVE-2021-21309: Redis is an open-source, in-memory database that persists on disk. In affected versions of Redis an integer overflow bug in 32-bit Redis version 4.0 or newer could be exploited to corrupt the heap and potentially result with remote code execution. Redis 4.0 or newer uses a configurable limit for the maximum supported bulk input size. By default, it is 512MB which is a safe value for all platforms. If the limit is significantly increased, receiving a large request from a client may trigger several integer overflow scenarios, which would result with buffer overflow and heap corruption. We believe this could in certain conditions be exploited for remote code execution. By default, authenticated Redis users have access to all configuration parameters and can therefore use the “CONFIG SET proto-max-bulk-len” to change the safe default, making the system vulnerable. **This problem only affects 32-bit Redis (on a 32-bit system, or as a 32-bit executable running on a 64-bit system).** The problem is fixed in version 6.2, and the fix is back ported to 6.0.11 and 5.0.11. Make sure you use one of these versions if you are running 32-bit Redis. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent clients from directly executing `CONFIG SET`: Using Redis 6.0 or newer, ACL configuration can be used to block the command. Using older versions, the `rename-command` configuration directive can be used to rename the command to a random string unknown to users, rendering it inaccessible. Please note that this workaround may have an additional impact on users or operational systems that expect `CONFIG SET` to behave in certain ways.

Assessing the Risk of CVE-2021-21309

Access Complexity Graph

The exploitability of CVE-2021-21309 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2021-21309

CVE-2021-21309 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2021-21309, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2021-21309, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2021-21309 has no significant impact on data confidentiality.
  • Integrity: Low
    Exploiting CVE-2021-21309 may cause minor changes to data without severely impacting its accuracy.
  • Availability: Low
    CVE-2021-21309 may slightly degrade system performance without fully affecting service availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.647% (probability of exploit)

EPSS Percentile: 79.61% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 20.39% of others.

CVE-2021-21309 References

External References

CWE Common Weakness Enumeration

CWE-190

CAPEC Common Attack Pattern Enumeration and Classification

  • Forced Integer Overflow CAPEC-92 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.

Vulnerable Configurations

  • cpe:2.3:a:redislabs:redis:4.0:-:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.10:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.10:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.11:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.11:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.12:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.12:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.13:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.13:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0.14:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0.14:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:4.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:4.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:5.0:-:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:5.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:5.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:5.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:5.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:5.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:5.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:5.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:5.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:5.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:5.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:5.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:5.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:5.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:5.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:5.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:5.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:5.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:5.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:5.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:5.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:5.0.10:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:5.0.10:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:6.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:6.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:6.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:6.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:6.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:6.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:6.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:6.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:6.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:6.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:6.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:6.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:6.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:6.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:6.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:6.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:6.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:6.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:6.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:6.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:redislabs:redis:6.0.10:*:*:*:*:*:*:*
    cpe:2.3:a:redislabs:redis:6.0.10:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2021-21309: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2130 – A vulnerability was found in OpenXE up to 1.12. It has been declared as problematic. This vulnerability affects unknown code of the component Ticke...
  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...