Hive has Double-free and Use After Free Vulnerabilities
Priority LOW 38CWE-415Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
`Drop` implementation for `Hive` did perform free, but so did `Hive::close`, which, at the end of the scope performed `Drop`, therefore triggering double-free. Additionally, function `Hive::from_handle` was not marked as unsafe, making it, in combination with `as_handle` easy to clone and trigger double-free in safe code or triggering UB when using invalid pointer.
Why it matters now
Fix Fixed hivex (crates.io): 0.2.1
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | hivex (crates.io) | 0.2.0 to before 0.2.1 | 0.2.1 | Patch available | GHSA-j8cj-hw74-64jv |
- hivex (crates.io) Vendor— Affected 0.2.0 to before 0.2.1 Fixed in 0.2.1 Patch available GHSA-j8cj-hw74-64jv
Remediation
- Fix · GHSA-j8cj-hw74-64jv hivex (crates.io) Fixed in 0.2.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-j8cj-hw74-64jv
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences