# CVE-2022-35951: Redis subject to Integer Overflow leading to Remote Code Execution via Heap Overflow

> An integer overflow in Redis XAUTOCLAIM command allows remote attackers to execute arbitrary code via heap overflow.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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:** 23 Sep 2022
- **Updated:** 23 Apr 2025
- **Also known as:** ALPINE-CVE-2022-35951, BIT-keydb-2022-35951, BIT-redis-2022-35951, BIT-valkey-2022-35951, CLEANSTART-2026-OG09584, DEBIAN-CVE-2022-35951, GHSA-5gc4-76rx-22c9, openSUSE-SU-2024:12361-1

## What is CVE-2022-35951?

CVE-2022-35951 is a high-severity vulnerability in Fedoraproject Fedora, published on 23 Sep 2022. 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. 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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2022-35951?

3 open source packages ship an affected version, including keydb, redis and valkey. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keydb` | Bitnami | From 7.0.0 | 7.0.5 |
| `redis` | Bitnami | From 7.0.0 | 7.0.5 |
| `valkey` | Bitnami | From 7.0.0 | 7.0.5 |
| `redis` | openSUSE:Tumbleweed | All versions | 7.0.5-1.1 |

Products: Fedoraproject Fedora, Redis Redis.

## How do I fix CVE-2022-35951?

Upgrade keydb to 7.0.5 or later.

## Is CVE-2022-35951 being exploited?

There is no known exploitation of CVE-2022-35951 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-35951 and fix it if it is affected.

What it is: CVE-2022-35951 is a high-severity vulnerability in Fedoraproject Fedora, published on 23 Sep 2022. 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-35951 in the wild and no public exploit code.

Affected packages and fixed versions:
- keydb (Bitnami): affected from 7.0.0; fixed in 7.0.5
- redis (Bitnami): affected from 7.0.0; fixed in 7.0.5
- valkey (Bitnami): affected from 7.0.0; fixed in 7.0.5

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-35951/ (Markdown: https://insights.sbomify.com/CVE-2022-35951/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-35951
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-35951
- OSV: https://osv.dev/vulnerability/CVE-2022-35951

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-35951/
Summaries are generated and may contain mistakes; the official description above is the record.