Code execution via XAUTOCLAIM reply-array overflow
Published Sep 23, 2022 · Updated Apr 23, 2025
Heap overflow in Redis 7.0.0 through 7.0.4 allows attackers to execute code through a crafted XAUTOCLAIM COUNT argument. In xautoclaimCommand, the COUNT limit tracks only claimed entries while deleted pending entries accumulate in an undersized temporary reply array, causing an out-of-bounds heap write. Exploitation requires command access and a stream consumer group with deleted entries in its pending list; success can crash the server or execute code in its process.
Summary
What happened
Heap overflow in Redis 7.0.0 through 7.0.4 allows attackers to execute code through a crafted XAUTOCLAIM COUNT argument. In xautoclaimCommand, the COUNT limit tracks only claimed entries while deleted pending entries accumulate in an undersized temporary reply array, causing an out-of-bounds heap write. Exploitation requires command access and a stream consumer group with deleted entries in its pending list; success can crash the server or execute code in its process.
The record
- CVE
- CVE-2022-35951
- Published
- Sep 23, 2022
- Updated
- Apr 23, 2025
- Vendor
- Redis
- Product
- Redis
- Classifications
- CWE-680, CWE-190
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 23, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 7.0.0, < 7.0.5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo