Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2023-36824: Heap overflow in COMMAND GETKEYS and ACL evaluation in Redis

HighCVSS 8.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Plan (action score 58/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 77.4% (FIRST EPSS); higher than 99.5% of all records.
  • 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.
  • Fixed version: redis (Alpine:v3.16) 7.0.12-r0; redis (Debian:12) 5:7.0.15-1~deb12u1; redis (Debian:13) 5:7.0.12-1.

Add it to your regular patch cycle. Upgrade to redis (Alpine:v3.16) 7.0.12-r0; redis (Debian:12) 5:7.0.15-1~deb12u1; redis (Debian:13) 5:7.0.12-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jul 11, 2023
Updated
Jun 17, 2026
EPSS
77.4% · 99th percentile

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.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-36824

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Is Redis on your server exposed to the internet?Run a port scan

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for redis records

Is Redis on your server exposed to the internet?Run a port scan

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
redisredis
fedoraprojectfedora

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

Watch new CVEs for redis

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or is weaponized

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Is Redis on your server exposed to the internet?Run a port scan

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every Monday

Is Redis on your server exposed to the internet?

The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.

Run a port scan

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

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

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:Leap 15.5redis7before 7.0.8-150500.3.3.17.0.8-150500.3.3.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

Same product

redis: all records

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…KEV
    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

Published before and after this one in the same product

  • ← EarlierCVE-2023-28856Apr 18, 2023 · `HINCRBYFLOAT` can be used to crash a redis-server process
    26Monitor
  • ← EarlierCVE-2023-31655May 18, 2023 · redis v7.0.10 was discovered to contain a segmentation violation.
    30Monitor
  • Later →CVE-2021-31294Jul 15, 2023 · Redis before 6cbea7d allows a replica to cause an assertion failure in a primary server by sending a non-administrative command…
    23Monitor

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.

Bug bounty scope

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

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.

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

Weakness class (CWE)

CWE-122 · Heap-based Buffer Overflow

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

—

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records