What is GHSA-J8CJ-HW74-64JV?

GHSA-J8CJ-HW74-64JV is a medium-severity use after free vulnerability in hivex (rust), affecting versions = 0.2.0. It is fixed in 0.2.1. Memory is accessed after it has been freed, leading to undefined behavior in native code.

Which versions of hivex are affected by GHSA-J8CJ-HW74-64JV?

hivex (rust) versions = 0.2.0 is affected.

Is there a fix for GHSA-J8CJ-HW74-64JV?

Yes. GHSA-J8CJ-HW74-64JV is fixed in 0.2.1. Upgrade to this version or later.

Is GHSA-J8CJ-HW74-64JV exploitable, and should I be worried?

Whether GHSA-J8CJ-HW74-64JV is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-J8CJ-HW74-64JV is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-J8CJ-HW74-64JV in hivex

Q: How do I fix GHSA-J8CJ-HW74-64JV?

Upgrade hivex to 0.2.1 or later.

Summary

Hive has Double-free and Use After Free Vulnerabilities

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.

Impact

Memory is accessed after it has been freed, leading to undefined behavior in native code. Typical impact: memory corruption, crash, or potential code execution.

Affected versions

hivex (= 0.2.0)

Security releases

hivex → 0.2.1 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade hivex to 0.2.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-J8CJ-HW74-64JV? GHSA-J8CJ-HW74-64JV is a medium-severity use after free vulnerability in hivex (rust), affecting versions = 0.2.0. It is fixed in 0.2.1. Memory is accessed after it has been freed, leading to undefined behavior in native code.
Which versions of hivex are affected by GHSA-J8CJ-HW74-64JV? hivex (rust) versions = 0.2.0 is affected.
Is there a fix for GHSA-J8CJ-HW74-64JV? Yes. GHSA-J8CJ-HW74-64JV is fixed in 0.2.1. Upgrade to this version or later.
Is GHSA-J8CJ-HW74-64JV exploitable, and should I be worried? Whether GHSA-J8CJ-HW74-64JV is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-J8CJ-HW74-64JV is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-J8CJ-HW74-64JV? Upgrade hivex to 0.2.1 or later.