Security readout for executives and security teams
Plain-English summary
Redis 7.0.0 through 7.0.11 has a heap overflow in key-name extraction used by COMMAND GETKEYS, COMMAND GETKEYSANDFLAGS, and some ACL checks. A successful attack could expose memory, corrupt Redis, or potentially execute code. The source bundle states Redis 7.0.12 patches it.
Executive priority
Prioritize remediation for production Redis 7.0 systems that support critical services, shared tenants, or broad internal access. The issue has high potential impact, but source evidence does not show confirmed exploitation. Patch during the next urgent maintenance window, faster for exposed or multi-user environments.
Technical view
The issue is a heap overflow in Redis command key extraction and ACL evaluation for variadic key-name handling. The described paths involve authenticated users issuing crafted key-inspection commands or commands subject to ACL key-name matching. The cited impact includes random heap memory reads, heap corruption, and possible remote code execution.
Likely exposure
Exposure is most relevant to Redis 7.0.x deployments before 7.0.12, especially where authenticated users, applications, or service accounts are less trusted or broadly permitted. Redis instances embedded in vendor products should be checked against vendor advisories.
Exploitation context
The provided sources do not establish active exploitation, and KEV is false. The advisory describes authenticated command scenarios with high complexity conditions. Treat internet-exposed or shared Redis environments as higher priority because valid credentials or overbroad application access can change business risk.
Researcher notes
Do not assume unauthenticated exploitation from the supplied bundle. Focus validation on version range, command permissions, ACL key-pattern usage, and Redis exposure boundaries. The CVSS vector and description should be reconciled with local threat modeling because the text emphasizes authenticated command execution.
Mitigation direction
- Upgrade Redis 7.0 deployments to 7.0.12 or later.
- Check OS or vendor package advisories for backported fixes.
- Review Redis ACLs and reduce broad command/key access where practical.
- Restrict Redis network access to trusted application paths only.
- Check affected vendor appliances against their published advisories.
Validation and detection
- Inventory Redis versions and flag 7.0.0 through 7.0.11.
- Confirm package build includes the Redis 7.0.12 fix or vendor backport.
- Review authenticated users allowed to run key-inspection or broad variadic-key commands.
- Verify Redis is not reachable from untrusted networks.
- Check vendor advisories for embedded Redis exposure status.
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-122: 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 lookupCWE-131: 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-2023-36824 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.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:N/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:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H1.45.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.4HighVector: CVSS:3.1/AV:L/AC:H/PR:N/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-4cfx-h9gq-xpx3CVE reference · x_refsource_CONFIRM
- https://github.com/redis/redis/releases/tag/7.0.12CVE reference · x_refsource_MISC
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TDNNH2ONMVNBQ6LUIAOAGDNFPKXNST5K/CVE reference
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MIF5MAGYARYUMRFK7PQI7HYXMK2HZE5T/CVE reference
- https://security.netapp.com/advisory/ntap-20230814-0009/CVE reference
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.
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Calculation of Buffer Size
Incorrect Calculation of Buffer Size represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.