Heap corruption via panic-triggered double drop
Published Apr 1, 2021 · Updated Aug 3, 2024
Double free in endian_trait 0.6.0 and earlier allows attackers to corrupt heap memory when a user-provided Endian implementation panics. The mutable-slice Endian methods use ptr::read() to duplicate ownership of each element before calling the trait method, without guarding panic unwinding. Reachability requires a consuming application to execute an attacker-influenced Endian implementation that panics; the demonstrated consequence is heap corruption and a process crash.
Summary
What happened
Double free in endian_trait 0.6.0 and earlier allows attackers to corrupt heap memory when a user-provided Endian implementation panics. The mutable-slice Endian methods use ptr::read() to duplicate ownership of each element before calling the trait method, without guarding panic unwinding. Reachability requires a consuming application to execute an attacker-influenced Endian implementation that panics; the demonstrated consequence is heap corruption and a process crash.
The record
- CVE
- CVE-2021-29929
- Published
- Apr 1, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1499.004
- 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.
Public exploit references
- Panic-triggered double-drop proof of conceptproof of concept · demonstrated
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