CVE-2022-35977 | Integer overflow in certain command arguments can drive Redis to OOM panic

Redis is an in-memory database that persists on disk. Authenticated users issuing specially crafted `SETRANGE` and `SORT(_RO)` commands can trigger an integer overflow, resulting with Redis attempting to allocate impossible amounts of memory and abort with an out-of-memory (OOM) panic. The problem is fixed in Redis versions 7.0.8, 6.2.9 and 6.0.17. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Published: 2023-01-20 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2022-35977 is rated Moderate Risk (50.4/100): CVSS Medium severity, with high exploitation likelihood (EPSS 11.79%, 96th percentile). Core evidence: EPSS ranks this CVE among the most likely to be exploited in the near term. Mandatory action: High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-35977

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 35.55% 11.79% -23.76%
2 2026-03-17 33.86% 35.55% +1.69%
3 2026-03-03 33.86%

Full EPSS history (21 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-35977

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 3.6 [email protected]
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 3.6 [email protected]

Weakness enumeration for CVE-2022-35977

OS Trackers for CVE-2022-35977

vendor priority summary link
alpine medium CVE-2022-35977: 1 source package rows (redis); 53 state rows across 8 repos (3.17-main, 3.18-main, 3.19-main, 3.20-community, 3.21-community, 3.22-community, edge-community, edge-main); fixed 8, open 45. https://security.alpinelinux.org/vuln/CVE-2022-35977
debian not yet assigned CVE-2022-35977 not yet assigned priority: Debian including 1 source packages (redis), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-35977
gentoo normal CVE-2022-35977: 1 GLSA(s) (202408-05), 1 atom(s) (dev-db/redis); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-35977
redhat medium https://access.redhat.com/security/cve/CVE-2022-35977
suse medium https://www.suse.com/security/cve/CVE-2022-35977/
ubuntu medium CVE-2022-35977 medium priority: Ubuntu including 1 source packages (redis), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): released 6, not-affected 5, ignored 2. https://ubuntu.com/security/CVE-2022-35977

Affected software / configurations for CVE-2022-35977

Vendor Product Version Raw CPE
redis redis >= 6.0.0, < 6.0.17 cpe:2.3:a:redis:redis:*:*:*:*:*:*:*:*
redis redis >= 6.2.0, < 6.2.9 cpe:2.3:a:redis:redis:*:*:*:*:*:*:*:*
redis redis >= 7.0.0, < 7.0.8 cpe:2.3:a:redis:redis:*:*:*:*:*:*:*:*

References for CVE-2022-35977

cvelogic Threat Intelligence