RedisDatabase / datastore
CVE-2023-36824
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRedis 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRedis 7.0 versions prior to 7.0.12 contain a heap overflow vulnerability in the key extraction logic used by COMMAND GETKEYS and COMMAND GETKEYSANDFLAGS commands, as well as in ACL rule matching for variadic key name arguments. This allows authenticated users to trigger heap corruption and potentially achieve remote code execution by executing specially crafted commands that cause the key name extraction to overflow its buffer.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
RedisDatabase / datastore
>= 7.0.0, < 7.0.12
FedoraOperating system
= 37= 38CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Redis versionRun `redis-server --version` or `redis-cli INFO server` to retrieve the Redis version numberAffected if Version is 7.0.0 or higher but below 7.0.12
-
Verify Redis is running with COMMAND GETKEYS enabledRun `redis-cli COMMAND GETKEYS` to confirm the command is available to authenticated clientsAffected if The command executes successfully without error, indicating it is accessible to authenticated users
-
Check for ACL-defined users with variadic key patternsRun `redis-cli ACL LIST` and examine ACL rules for patterns containing multiple key names or key wildcard expressions in the selector rulesAffected if ACL rules contain user definitions with variadic key name arguments that could trigger the affected key name extraction logic
Your environment is affected if you run Redis version 7.0.0 through 7.0.11 and have authenticated users who can execute COMMAND GETKEYS/COMMAND GETKEYSANDFLAGS or use ACL rules with variadic key name arguments.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.0.12
Upgrade Redis to version 7.0.12 or later to patch the vulnerability. There are no reliable workarounds; upgrading is the only effective mitigation.
Redis 7.0.12 (or latest stable 7.x release)
- Identify current Redis version using 'redis-server --version' or 'redis-cli INFO'
- If running Redis 7.0.0-7.0.11, upgrade to Redis 7.0.12 or later
- For Fedora systems, run 'sudo dnf update redis' to apply available security updates
- After upgrade, restart the Redis service: 'sudo systemctl restart redis'
- Verify the new version is running: 'redis-cli INFO | grep redis_version'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Redis
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36824 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-36824 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data