Memory corruption via overflowing reply-array allocation
Published Oct 4, 2021 · Updated Aug 3, 2024
Integer overflow in the Hiredis reply parser before 1.0.1 allows attackers to corrupt memory via a crafted RESP multi-bulk reply. createArrayObject multiplies the untrusted element count by the pointer size for calloc without first rejecting values that exceed SIZE_MAX. The client must parse attacker-controlled or corrupted RESP data, and the default element limit leaves 64-bit builds likely unaffected.
Summary
What happened
Integer overflow in the Hiredis reply parser before 1.0.1 allows attackers to corrupt memory via a crafted RESP multi-bulk reply. createArrayObject multiplies the untrusted element count by the pointer size for calloc without first rejecting values that exceed SIZE_MAX. The client must parse attacker-controlled or corrupted RESP data, and the default element limit leaves 64-bit builds likely unaffected.
The record
- CVE
- CVE-2021-32765
- Published
- Oct 4, 2021
- Updated
- Aug 3, 2024
- Vendor
- Redis
- Product
- Hiredis
- Classifications
- CWE-190, CWE-680, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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