Security readout for executives and security teams
Plain-English summary
CVE-2021-32625 is a Redis heap-corruption issue in the STRALGO LCS command. A client with Redis access could potentially trigger remote code execution, especially on affected 32-bit systems. It is high severity, but exploitation requires Redis client privileges and high attack complexity.
Executive priority
Treat as a high-priority infrastructure fix for Redis instances reachable by applications, users, or partners. Patch or restrict the command promptly, prioritizing internet-exposed and shared Redis services. No source provided evidence of active exploitation, so response should be urgent but not emergency-driven.
Technical view
Redis 6.0 or newer had an integer overflow in STRALGO LCS, an incomplete fix for CVE-2021-29477. The flaw can corrupt heap memory and potentially lead to remote code execution. Fixed versions are 6.0.14 and 6.2.4. Sources identify CWE-680 and CVSS 3.1 score 7.5.
Likely exposure
Exposure is most likely where Redis 6.0.x before 6.0.14 or 6.2.x before 6.2.4 is reachable by untrusted or weakly trusted clients. Risk depends on ACLs, STRALGO LCS availability, platform architecture, and proto-max-bulk-len configuration on relevant 64-bit deployments.
Exploitation context
The provided sources do not show known active exploitation, and the CVE is not listed as KEV. The CVSS vector requires network access and low privileges, with high attack complexity and no user interaction.
Researcher notes
The advisory frames this as an incomplete CVE-2021-29477 fix. Validate architecture and configuration before judging exploitability. Avoid assuming 64-bit systems are unaffected; the source names a configuration condition for 64-bit systems with prior fixes. Evidence is limited to vendor and distribution advisories.
Mitigation direction
- Upgrade Redis to 6.0.14, 6.2.4, or a later vendor-supported release.
- Use Redis ACLs to block client use of STRALGO LCS if immediate patching is not possible.
- On relevant 64-bit systems, keep proto-max-bulk-len below 2GB; default is 512MB.
- Check operating-system vendor advisories for packaged Redis updates and backports.
Validation and detection
- Inventory Redis servers and record exact version, branch, architecture, and package source.
- Confirm whether STRALGO LCS is accessible to application or user-controlled clients.
- Review Redis ACL rules for command restrictions affecting STRALGO LCS.
- Verify proto-max-bulk-len is below 2GB where the 64-bit workaround applies.
- Confirm patched package versions against Redis and distribution advisories.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupExecution 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 lookupDatabase 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 lookupCVE-2021-32625 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H1.65.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/redis/redis/security/advisories/GHSA-46cp-x4x9-6pfqCVE reference · x_refsource_CONFIRM
- https://github.com/redis/redis/releases/tag/6.0.14CVE reference · x_refsource_MISC
- https://github.com/redis/redis/releases/tag/6.2.4CVE reference · x_refsource_MISC
- FEDORA-2021-916f861096CVE reference · vendor-advisory, x_refsource_FEDORA
- FEDORA-2021-0ad4bec5b1CVE reference · vendor-advisory, x_refsource_FEDORA
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.