# CVE-2022-35977: Integer overflow in certain command arguments can drive Redis to OOM panic > Authenticated users can trigger an integer overflow via crafted commands, causing Redis to crash due to out-of-memory errors. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Jan 2023 - **Updated:** 3 Nov 2025 - **Also known as:** ALPINE-CVE-2022-35977, AZL-13125, BIT-keydb-2022-35977, BIT-redis-2022-35977, BIT-valkey-2022-35977, CLEANSTART-2026-QI92369, DEBIAN-CVE-2022-35977, GHSA-mrcw-fhw9-fj8j, SUSE-SU-2023:0274-1, UBUNTU-CVE-2022-35977 ## What is CVE-2022-35977? CVE-2022-35977 is a medium-severity vulnerability in redis, published on 20 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2022-35977? 3 open source packages ship an affected version, including redis, keydb and valkey. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `redis` | Bitnami | From 6.0.0 | 6.0.17, 6.2.9, 7.0.8 | | `keydb` | Bitnami | From 6.0.0 | 6.0.17, 6.2.9, 7.0.8 | | `valkey` | Bitnami | From 6.0.0 | 6.0.17, 6.2.9, 7.0.8 | | `redis` | SUSE:Enterprise Storage 7 | All versions | 6.0.14-150200.6.17.1 | | `redis` | SUSE:Enterprise Storage 7.1 | All versions | 6.0.14-150200.6.17.1 | | `redis` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 6.0.14-150200.6.17.1 | | `redis` | SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | All versions | 6.0.14-150200.6.17.1 | | `redis` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 6.0.14-150200.6.17.1 | | `redis` | SUSE:Linux Enterprise Real Time 15 SP3 | All versions | 6.0.14-150200.6.17.1 | | `redis` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 6.0.14-150200.6.17.1 | | `redis` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 6.0.14-150200.6.17.1 | | `redis` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 6.0.14-150200.6.17.1 | | `redis` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 6.0.14-150200.6.17.1 | | `redis` | SUSE:Manager Proxy 4.2 | All versions | 6.0.14-150200.6.17.1 | | `redis` | SUSE:Manager Retail Branch Server 4.2 | All versions | 6.0.14-150200.6.17.1 | | `redis` | SUSE:Manager Server 4.2 | All versions | 6.0.14-150200.6.17.1 | Products: Redis Redis. ## How do I fix CVE-2022-35977? Upgrade redis to a fixed version for your release line: 6.0.17, 6.2.9 or 7.0.8. ## Is CVE-2022-35977 being exploited? There is no known exploitation of CVE-2022-35977 in the wild and no public exploit code. ## Other vulnerabilities in redis - [CVE-2022-0543](https://insights.sbomify.com/CVE-2022-0543/): Debian-specific Redis Server Lua Sandbox Escape (critical 10.0, exploited in the wild) - [CVE-2026-23479](https://insights.sbomify.com/CVE-2026-23479/): redis-server use-after-free in unblock client flow may allow remote code execution (high 7.7) - [CVE-2026-25243](https://insights.sbomify.com/CVE-2026-25243/): redis-server RESTORE invalid memory access may allow remote code execution (high 7.7) - [CVE-2025-62507](https://insights.sbomify.com/CVE-2025-62507/): Redis: Bug in XACKDEL may lead to stack overflow and potential RCE (high 7.7) - [CVE-2025-48367](https://insights.sbomify.com/CVE-2025-48367/): Redis DoS Vulnerability due to bad connection error handling (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-35977 and fix it if it is affected. What it is: CVE-2022-35977 is a medium-severity vulnerability in redis, published on 20 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-35977 in the wild and no public exploit code. Affected packages and fixed versions: - redis (Bitnami): affected from 6.0.0; fixed in 6.0.17, 6.2.9, 7.0.8 - keydb (Bitnami): affected from 6.0.0; fixed in 6.0.17, 6.2.9, 7.0.8 - valkey (Bitnami): affected from 6.0.0; fixed in 6.0.17, 6.2.9, 7.0.8 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-35977/ (Markdown: https://insights.sbomify.com/CVE-2022-35977/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-35977 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-35977 - OSV: https://osv.dev/vulnerability/CVE-2022-35977 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-35977/ Summaries are generated and may contain mistakes; the official description above is the record.