Application crash via unchecked allocation results
Published Jan 16, 2020 · Updated Aug 4, 2024
NULL pointer dereference in Redis Labs Hiredis 0.14.0 and earlier allows remote attackers to crash dependent applications after allocation failure. In async.c and dict.c, allocation results are passed to memcpy or dereferenced without checking whether malloc returned NULL. Reachability requires an allocation failure; the demonstrated consequence is a dependent-process crash and service interruption, not data disclosure or modification.
Summary
What happened
NULL pointer dereference in Redis Labs Hiredis 0.14.0 and earlier allows remote attackers to crash dependent applications after allocation failure. In async.c and dict.c, allocation results are passed to memcpy or dereferenced without checking whether malloc returned NULL. Reachability requires an allocation failure; the demonstrated consequence is a dependent-process crash and service interruption, not data disclosure or modification.
The record
- CVE
- CVE-2020-7105
- Published
- Jan 16, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 16, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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