Denial of service via unreleased stream iterator
Published Jun 22, 2022 · Updated Aug 3, 2024
Memory leak in stream handling in Redis 7.0.0 allows remote attackers to exhaust server memory via repeated stream commands. streamGetEdgeID starts a stream iterator but returns without calling streamIteratorStop, leaving iterator stack allocations unreleased. Large streams can require heap-backed iterator stacks, so repeated XADD or XTRIM operations can consume memory and interrupt the Redis service.
Summary
What happened
Memory leak in stream handling in Redis 7.0.0 allows remote attackers to exhaust server memory via repeated stream commands. streamGetEdgeID starts a stream iterator but returns without calling streamIteratorStop, leaving iterator stack allocations unreleased. Large streams can require heap-backed iterator stacks, so repeated XADD or XTRIM operations can consume memory and interrupt the Redis service.
The record
- CVE
- CVE-2022-33105
- Published
- Jun 22, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 22, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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