RedisDatabase / datastore
CVE-2022-31144
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. A specially crafted `XAUTOCLAIM` command on a stream key in a specific state may result with heap overflow, and potentially remote code execution. This problem affects versions on the 7.x branch prior to 7.0.4. The patch is released in version 7.0.4.
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 · moderate confidenceHeap overflow vulnerability in Redis XAUTOCLAIM command on stream keys in a specific state, potentially allowing remote code execution. The overflow occurs due to insufficient bounds checking when processing certain stream key states.
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, < 7.0.4CVSS 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 exact version numberAffected if The version is >= 7.0.0 and < 7.0.4
-
Identify active stream keysUse `redis-cli KEYS '*'` to find keys, then `redis-cli TYPE <key>` to identify stream types, or query `redis-cli XINFO STREAM <key>` on known stream keysAffected if Stream keys exist in the database and Redis version is in the affected range
-
Verify XAUTOCLAIM command usageEnable slow logging with `redis-cli CONFIG SET slowlog-log-slower-than 0` and check `redis-cli SLOWLOG GET` for recent XAUTOCLAIM commands, or monitor with `redis-cli MONITOR`Affected if XAUTOCLAIM has been executed on stream keys and the Redis version is vulnerable
-
Check network exposureReview Redis bind configuration with `redis-cli CONFIG GET bind` and firewall rules to determine if Redis is accessible from untrusted networksAffected if Redis is bound to non-localhost interfaces and is version vulnerable
A user is affected if their Redis version is 7.0.0 through 7.0.3 inclusive, they use stream keys, and the XAUTOCLAIM command has been or can be executed against stream keys in a vulnerable state.
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.4
Upgrade Redis to version 7.0.4 or later to patch the heap overflow vulnerability. If immediate upgrade is not feasible, restrict access to Redis instances to trusted networks only.
Redis 7.0.4
- Backup your Redis data and configuration files
- Stop the Redis service
- Upgrade Redis to version 7.0.4 or later using your package manager or compilation (e.g., yum update redis, apt update redis, or compile from source)
- Verify the installed Redis version is 7.0.4 or later using `redis-server --version`
- Start the Redis service
- Test that the XAUTOCLAIM command works correctly on stream keys
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Redis
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31144 — 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-2022-31144 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