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

> Authenticated users can trigger a heap overflow in Redis via crafted commands, potentially leading to remote code execution or memory disclosure.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jul 2023
- **Updated:** 13 Feb 2025
- **Also known as:** ALPINE-CVE-2023-36824, BELL-CVE-2023-36824, BIT-keydb-2023-36824, BIT-redis-2023-36824, BIT-valkey-2023-36824, CLEANSTART-2026-FC95415, DEBIAN-CVE-2023-36824, GHSA-4cfx-h9gq-xpx3

## What is CVE-2023-36824?

CVE-2023-36824 is a high-severity memory corruption vulnerability in Fedoraproject Fedora, published on 11 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-131 (Incorrect Calculation of Buffer Size), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2023-36824?

3 open source packages ship an affected version, including keydb, redis and valkey. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keydb` | Bitnami | From 7.0.0 | 7.0.12 |
| `redis` | Bitnami | From 7.0.0 | 7.0.12 |
| `valkey` | Bitnami | From 7.0.0 | 7.0.12 |

Products: Fedoraproject Fedora, Redis Redis.

## How do I fix CVE-2023-36824?

Upgrade keydb to 7.0.12 or later.

## Is CVE-2023-36824 being exploited?

There is no known exploitation of CVE-2023-36824 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-36824 and fix it if it is affected.

What it is: CVE-2023-36824 is a high-severity memory corruption vulnerability in Fedoraproject Fedora, published on 11 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-36824 in the wild and no public exploit code.

Affected packages and fixed versions:
- keydb (Bitnami): affected from 7.0.0; fixed in 7.0.12
- redis (Bitnami): affected from 7.0.0; fixed in 7.0.12
- valkey (Bitnami): affected from 7.0.0; fixed in 7.0.12

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-36824/ (Markdown: https://insights.sbomify.com/CVE-2023-36824/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-36824
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-36824
- OSV: https://osv.dev/vulnerability/CVE-2023-36824

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-36824/
Summaries are generated and may contain mistakes; the official description above is the record.