Heap corruption via premature slice length update
Published Apr 1, 2021 · Updated Aug 3, 2024
Heap memory corruption in the arenavec crate through 0.1.1 allows attackers to crash a consuming process through a panicking T::default(). common::Slice::<T, H>::new records the full slice length before initializing every element, so unwinding drops uninitialized T values. Reachability requires consuming code to call Slice::new with a Default implementation that panics; the bounded result is heap corruption and process termination.
Summary
What happened
Heap memory corruption in the arenavec crate through 0.1.1 allows attackers to crash a consuming process through a panicking T::default(). common::Slice::<T, H>::new records the full slice length before initializing every element, so unwinding drops uninitialized T values. Reachability requires consuming code to call Slice::new with a Default implementation that panics; the bounded result is heap corruption and process termination.
The record
- CVE
- CVE-2021-29930
- Published
- Apr 1, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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