dbcve.org
RedisDatabase / datastore

CVE-2022-24834

HIGH · 8.8 CVSS v3.1 Published 2023-07-13
Fix available
A fix is available. Upgrade to 6.0.20 / 6.2.13 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Redis is an in-memory database that persists on disk. A specially crafted Lua script executing in Redis can trigger a heap overflow in the cjson library, and result with heap corruption and potentially remote code execution. The problem exists in all versions of Redis with Lua scripting support, starting from 2.6, and affects only authenticated and authorized users. The problem is fixed in versions 7.0.12, 6.2.13, and 6.0.20.

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 confidence

A specially crafted Lua script executing in Redis triggers a heap overflow in the cjson library, leading to heap corruption and potentially remote code execution. This vulnerability affects all Redis versions with Lua scripting support from 2.6 onward and requires authenticated user access.

MitigationUpgrade Redis to versions 7.0.12, 6.2.13, or 6.0.20 or later. If Lua scripting is not required, consider disabling it as a defense-in-depth measure.

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
Affected:>= 2.6.0, < 6.0.20>= 6.2.0, < 6.2.13>= 7.0.0, < 7.0.12
FedoraOperating system
Affected:= 37= 38

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Redis version
    Run 'redis-server --version' or 'redis-cli INFO server' to obtain the exact version number
    Affected if The version falls outside these safe versions: 6.0.20+, 6.2.13+, or 7.0.12+ (i.e., it is >= 2.6.0 but < 6.0.20, OR >= 6.2.0 but < 6.2.13, OR >= 7.0.0 but < 7.0.12)
  2. Verify Lua scripting is enabled
    Run 'redis-cli CONFIG GET lua-time-limit' - a returned value confirms Lua support is active
    Affected if Lua scripting is enabled (the command returns a numeric value rather than an error)
  3. Confirm authentication is required for Redis
    Run 'redis-cli CONFIG GET requirepass' to check if a password is configured
    Affected if No password is set (empty requirepass) and the instance is exposed to untrusted network access, because the CVE requires authenticated user access to be exploitable

You are affected if your Redis version is vulnerable (not 6.0.20+, 6.2.13+, or 7.0.12+) AND Lua scripting is enabled AND your instance permits unauthenticated access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.0.20 / 6.2.13 / 7.0.12 or later
Fixed in 6.0.206.2.137.0.12
Interim mitigation

Upgrade Redis to versions 7.0.12, 6.2.13, or 6.0.20 or later. If Lua scripting is not required, consider disabling it as a defense-in-depth measure.

Recommended fix High confidence

Upgrade to Redis 7.0.12, 6.2.13, or 6.0.20 (choose the release line appropriate for your environment)

  1. 1. Identify current Redis version by running 'redis-server --version' or 'redis-cli INFO server'
  2. 2. Stop the Redis service: 'sudo systemctl stop redis' (or 'sudo service redis stop')
  3. 3. Backup Redis configuration files (usually /etc/redis/redis.conf) and data directory (usually /var/lib/redis/)
  4. 4. Upgrade Redis to a fixed version: 7.0.12, 6.2.13, or 6.0.20 (using your package manager: 'sudo dnf upgrade redis' on Fedora, or download from redis.io for other systems)
  5. 5. Verify the installed version matches a fixed release: 'redis-server --version'
  6. 6. Review Redis 7.0/6.2/6.0 release notes for any configuration changes needed
  7. 7. Start the Redis service: 'sudo systemctl start redis' (or 'sudo service redis start')
  8. 8. Verify Redis is operational: 'redis-cli ping' (should return PONG)
Caveat Minor version upgrades within the same major.minor series typically have minimal breaking changes, but review release notes for any deprecated features or configuration adjustments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Redis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24834 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24834 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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