dbcve.org
RedisDatabase / datastore

CVE-2022-36021

MEDIUM · 5.5 CVSS v3.1 Published 2023-03-01
Fix available
A fix is available. Upgrade to 6.0.18 / 6.2.11 or later.
See remediation →
57/100
Remediation priority · Elevated
High EPSS Zero-click Patch available

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. Authenticated users can use string matching commands (like `SCAN` or `KEYS`) with a specially crafted pattern to trigger a denial-of-service attack on Redis, causing it to hang and consume 100% CPU time. The problem is fixed in Redis versions 6.0.18, 6.2.11, 7.0.9.

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

A detailed technical summary for this CVE is being prepared.

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:< 6.0.18>= 6.2.0, < 6.2.11>= 7.0.0, < 7.0.9

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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.18 / 6.2.11 / 7.0.9 or later
Fixed in 6.0.186.2.117.0.9
Vendor patch github.com →
Recommended fix High confidence

Redis 6.0.18, 6.2.11, or 7.0.9 (choose based on current major.minor version)

  1. 1. Identify current Redis version by running `redis-cli INFO server` or `redis-server --version`
  2. 2. Based on current version, determine the appropriate target: if using 6.0.x, upgrade to 6.0.18; if using 6.2.x, upgrade to 6.2.11; if using 7.0.x, upgrade to 7.0.9
  3. 3. Back up Redis data using `redis-cli BGSAVE` and ensure persistence files are saved
  4. 4. Stop Redis service: `systemctl stop redis` or appropriate service command
  5. 5. Upgrade Redis package using system package manager (e.g., `apt-get update && apt-get install redis-server` or `yum update redis`)
  6. 6. Start Redis service: `systemctl start redis`
  7. 7. Verify version: `redis-cli INFO server` should show the updated version
  8. 8. Test application functionality to confirm normal operation
Caveat Upgrading between major versions (e.g., 6.x to 7.x) may have breaking changes; review Redis 7.0 release notes before such upgrades

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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