Skip to content
Noroxi
CVE-2023-36824· NVD / CVE Program· CNA GitHub_M

Heap overflow in COMMAND GETKEYS and ACL evaluation in Redis

Redis is an in-memory database that persists on disk. In Redit 7.0 prior to 7.0.12, extracting key names from a command and a list of arguments may, in some cases, trigger a heap overflow and result in reading random heap memory, heap corruption and potentially remote code execution. Several scenarios that may lead to authenticated users executing a specially crafted `COMMAND GETKEYS` or `COMMAND GETKEYSANDFLAGS`and authenticated users who were set with ACL rules that match key names, executing a specially crafted command that refers to a variadic list of key names. The vulnerability is patched in Redis 7.0.12.

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Jul 11, 2023
Updated
Jun 17, 2026
EPSS
77.4% · 100th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

58

Plan

Add it to your regular patch cycle.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
23 / 30 · 77.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.8
CNA · GitHub_M
7.4
1.4 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
redisredis
fedoraprojectfedora

Using redis? Add it to your stack and be the first to know about CVEs like this one. (Redis)

Add to my stack

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • redis redis7.0.0 and later · before 7.0.12

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • redis redis

    • >= 7.0.0, < 7.0.12affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.16redisfrom 7.0.0 · before 7.0.12-r07.0.12-r0
Debian:12redisbefore 5:7.0.15-1~deb12u15:7.0.15-1~deb12u1
Debian:13redisbefore 5:7.0.12-15:7.0.12-1
openSUSE:Tumbleweedredisbefore 7.0.12-1.17.0.12-1.1
SUSE:Linux Enterprise Module for Server Applications 15 SP5redis7before 7.0.8-150500.3.3.17.0.8-150500.3.3.1
SUSE:Linux Enterprise Module for Server Applications 15 SP5redis7before 7.0.8-150500.3.3.17.0.8-150500.3.3.1

Other highest-scoring records for the same primary product.

  • CVE-2022-0543It was discovered, that redis, a persistent key-value database, due to a packaging issue, is prone to a (Debian-specific) Lua sandbox escapeKEV
    100Now
  • CVE-2025-49844Redis Lua Use-After-Free may lead to remote code execution
    64This week
  • CVE-2022-24834Heap overflow issue with the Lua cjson library used by Redis
    47Plan
  • CVE-2023-22458Integer overflow in multiple Redis commands can lead to denial-of-service
    44Plan
  • CVE-2024-46981Redis' Lua library commands may lead to remote code execution
    41Plan
  • CVE-2022-36021Redis string pattern matching can be abused to achieve Denial of Service
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Alpine:redis7.0.12-r0 · Alpine:v3.16Package registry (OSV)
Debian:redis5:7.0.15-1~deb12u1 · Debian:12Package registry (OSV)
openSUSE:redis7.0.12-1.1 · openSUSE:TumbleweedPackage registry (OSV)
openSUSE:redis77.0.8-150500.3.3.1 · openSUSE:Leap 15.5Package registry (OSV)
SUSE:redis77.0.8-150500.3.3.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records