LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32761: Integer overflow issues with *BIT commands on 32-bit systems

Redis is an in-memory database that persists on disk. A vulnerability involving out-of-bounds read and integer overflow to buffer overflow exists starting with version 2.2 and prior to versions 5.0.13, 6.0.15, and 6.2.5. On 32-bit systems, Redis `*BIT*` command are vulnerable to integer overflow that can potentially be exploited to corrupt the heap, leak arbitrary heap contents or trigger remote code execution. The vulnerability involves changing the default `proto-max-bulk-len` configuration parameter to a very large value and constructing specially crafted commands bit commands. This problem only affects Redis on 32-bit platforms, or compiled as a 32-bit binary. Redis versions 5.0.`3m 6.0.15, and 6.2.5 contain patches for this issue. An additional workaround to mitigate the problem without patching the `redis-server` executable is to prevent users from modifying the `proto-max-bulk-len` configuration parameter. This can be done using ACL to restrict unprivileged users from using the CONFIG SET command.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Redis flaw affects only 32-bit platforms or 32-bit Redis builds. If exploitable conditions exist, a low-privileged user could cause memory corruption, expose heap data, crash the service, or potentially run code. Most 64-bit deployments are likely unaffected, but legacy or embedded Redis instances need focused review.

Executive priority

Treat this as high priority for any 32-bit Redis estate or product dependency. For confirmed 64-bit-only deployments, urgency is lower, but asset validation is still needed because the impact is severe when conditions match.

Technical view

Redis versions from 2.2 through fixed releases are affected by integer overflow and out-of-bounds read issues in BIT-family commands on 32-bit builds. The issue involves a very large proto-max-bulk-len setting and crafted BIT commands, with possible heap corruption, heap disclosure, denial of service, or remote code execution.

Likely exposure

Exposure is most likely in legacy, embedded, appliance, or distribution-packaged Redis running on 32-bit systems. Standard 64-bit Redis deployments are not identified as affected by the source bundle.

Exploitation context

The bundle does not report CISA KEV listing or active exploitation. Exploitation is not described as trivial: CVSS marks attack complexity high and privileges required low, and the vulnerable path depends on configuration conditions.

Researcher notes

Relevant weaknesses are CWE-125 and CWE-680. Focus validation on architecture, exact Redis version, package backports, ACL control over configuration changes, and whether untrusted authenticated users can reach BIT-command functionality. Do not assume exploit activity from this bundle.

Mitigation direction

  • Upgrade Redis to 5.0.13, 6.0.15, 6.2.5, or later supported vendor packages.
  • Restrict unprivileged users from changing proto-max-bulk-len through CONFIG SET.
  • Apply relevant Debian, Fedora, Gentoo, NetApp, or other vendor security updates.
  • Review exposed Redis access; reduce network reachability to trusted clients only.
  • Check current vendor guidance if running Redis in bundled appliances or managed products.

Validation and detection

  • Inventory Redis versions and confirm whether each instance is 32-bit or 64-bit.
  • Check whether deployed versions fall below 5.0.13, 6.0.15, or 6.2.5.
  • Review ACLs for who can modify Redis configuration values.
  • Identify Redis instances reachable by untrusted users or applications.
  • Confirm operating-system packages include the vendor security update.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-680: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32761 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H1.65.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-32761Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
redisredis>= 2.2, < 5.0.13, >= 6.0.0, < 6.0.15, >= 6.2.0, < 6.2.5Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-680 · source CWE mapping

Integer Overflow to Buffer Overflow

Integer Overflow to Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.