dbcve.org
RedisDatabase / datastore

CVE-2022-35951

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to 7.0.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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. Versions 7.0.0 and above, prior to 7.0.5 are vulnerable to an Integer Overflow. Executing an `XAUTOCLAIM` command on a stream key in a specific state, with a specially crafted `COUNT` argument may cause an integer overflow, a subsequent heap overflow, and potentially lead to remote code execution. This has been patched in Redis version 7.0.5. No known workarounds exist.

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

Redis versions 7.0.0 through 7.0.4 contain an integer overflow vulnerability in the XAUTOCLAIM command. When executing this command on a stream key in a specific state with a specially crafted COUNT argument, an integer overflow occurs, leading to a heap overflow that can potentially be exploited for remote code execution.

MitigationUpgrade Redis to version 7.0.5 or later. No workarounds exist for this vulnerability.

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:>= 7.0.0, < 7.0.5
FedoraOperating system
Affected:= 37

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 | grep redis_version' to determine the exact version
    Affected if Version is 7.0.0, 7.0.1, 7.0.2, 7.0.3, or 7.0.4 (versions 7.0.0 through 7.0.4 are affected)
  2. Verify streams module availability
    Run 'redis-cli INFO modules | grep -i stream' or check if XAUTOCLAIM command exists with 'redis-cli COMMAND INFO xautoclaim'
    Affected if Streams are enabled and XAUTOCLAIM command is available (streams are built-in and enabled by default in Redis 7.x)
  3. Confirm Redis executable path
    Run 'which redis-server' or 'which redis-cli' to identify the Redis binary being used
    Affected if The binary is from a Redis 7.0.0-7.0.4 installation or a Fedora 37 Redis package
  4. Check for stream keys in database
    Run 'redis-cli --scan --pattern '*' | head -1000 | xargs -I {} redis-cli TYPE {}' to scan for stream-type keys, or check specific known stream keys with 'redis-cli TYPE <keyname>'
    Affected if Any stream keys exist in the database - the vulnerability triggers when XAUTOCLAIM is executed on a stream key

You are affected if you are running Redis versions 7.0.0 through 7.0.4 and have streams enabled with stream keys that can be processed by XAUTOCLAIM.

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 7.0.5 or later
Fixed in 7.0.5
Interim mitigation

Upgrade Redis to version 7.0.5 or later. No workarounds exist for this vulnerability.

Recommended fix High confidence

Redis 7.0.5

  1. 1. Identify the current Redis version by running `redis-server --version` or `redis-cli INFO server`
  2. 2. Stop the Redis server safely: `redis-cli SHUTDOWN NOSAVE` or `systemctl stop redis`
  3. 3. Update package repositories: `dnf check-update` (Fedora) or use your system's package manager
  4. 4. Install Redis 7.0.5 or later: `dnf update redis` (Fedora) or `apt-get update && apt-get install redis-server` (Debian/Ubuntu)
  5. 5. Verify the new version: `redis-server --version` should show 7.0.5 or higher
  6. 6. Start the Redis server: `redis-server &` or `systemctl start redis`
  7. 7. Verify Redis is running: `redis-cli PING` should return PONG

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-35951 — 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-35951 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