rustsec-2026-0029
Vulnerability from osv_rustsec
Published
2026-02-26 12:00
Modified
2026-03-01 06:01
Summary
Double-free and use-after-free for Hive
Details
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.
{
"affected": [
{
"database_specific": {
"categories": [],
"cvss": null,
"informational": "unsound"
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [
"hivex::Hive::close",
"hivex::Hive::from_handle"
],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "hivex",
"purl": "pkg:cargo/hivex"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
},
{
"fixed": "0.2.1"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"GHSA-j8cj-hw74-64jv"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "`Drop` implementation for `Hive` did perform free, but so did `Hive::close`, which,\nat the end of the scope performed `Drop`, therefore triggering double-free.\n\nAdditionally, function `Hive::from_handle` was not marked as unsafe, making it,\nin combination with `as_handle` easy to clone and trigger double-free in safe\ncode or triggering UB when using invalid pointer.",
"id": "RUSTSEC-2026-0029",
"modified": "2026-03-01T06:01:36Z",
"published": "2026-02-26T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/hivex"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0029.html"
},
{
"type": "WEB",
"url": "https://codeberg.org/1millibyte/toolsnt/issues/18"
}
],
"related": [],
"severity": [],
"summary": "Double-free and use-after-free for Hive"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…