What is GHSA-9GHP-W2HM-VFPF?

GHSA-9GHP-W2HM-VFPF is a medium-severity security vulnerability in wasmtime-jit-debug (rust), affecting versions < 24.0.0. It is fixed in 24.0.0.

Which versions of wasmtime-jit-debug are affected by GHSA-9GHP-W2HM-VFPF?

wasmtime-jit-debug (rust) versions < 24.0.0 is affected.

Is there a fix for GHSA-9GHP-W2HM-VFPF?

Yes. GHSA-9GHP-W2HM-VFPF is fixed in 24.0.0. Upgrade to this version or later.

Is GHSA-9GHP-W2HM-VFPF exploitable, and should I be worried?

Whether GHSA-9GHP-W2HM-VFPF 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-9GHP-W2HM-VFPF 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-9GHP-W2HM-VFPF in wasmtime-jit-debug

Q: Which versions of wasmtime-jit-debug are affected by GHSA-9GHP-W2HM-VFPF?

wasmtime-jit-debug (rust) versions < 24.0.0 is affected.

Q: Is there a fix for GHSA-9GHP-W2HM-VFPF?

Yes. GHSA-9GHP-W2HM-VFPF is fixed in 24.0.0. Upgrade to this version or later.

Q: Is GHSA-9GHP-W2HM-VFPF exploitable, and should I be worried?

Whether GHSA-9GHP-W2HM-VFPF 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.

Q: What actually determines whether GHSA-9GHP-W2HM-VFPF 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.

Q: How do I fix GHSA-9GHP-W2HM-VFPF?

Upgrade wasmtime-jit-debug to 24.0.0 or later.

Summary

wasmtimejitdebug Dumps Undefined Memory by JitDumpFile

The unsound function dump_code_load_record uses from_raw_parts to directly convert the pointer addr and len into a slice without any validation and that memory block would be dumped.

Thus, the 'safe' function dump_code_load_record is actually 'unsafe' since it requires the caller to guarantee that the addr is valid and len must not overflow. Otherwise, the function could dump the memory into file illegally, causing memory leak.

Note: this is an internal-only crate in the Wasmtime project not intended for external use and is more strongly signaled nowadays as of bytecodealliance/wasmtime#10963. Please open an issue in Wasmtime if you're using this crate directly.

Impact

Affected versions

wasmtime-jit-debug (< 24.0.0)

Security releases

wasmtime-jit-debug → 24.0.0 (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 wasmtime-jit-debug to 24.0.0 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-9GHP-W2HM-VFPF? GHSA-9GHP-W2HM-VFPF is a medium-severity security vulnerability in wasmtime-jit-debug (rust), affecting versions < 24.0.0. It is fixed in 24.0.0.
Which versions of wasmtime-jit-debug are affected by GHSA-9GHP-W2HM-VFPF? wasmtime-jit-debug (rust) versions < 24.0.0 is affected.
Is there a fix for GHSA-9GHP-W2HM-VFPF? Yes. GHSA-9GHP-W2HM-VFPF is fixed in 24.0.0. Upgrade to this version or later.
Is GHSA-9GHP-W2HM-VFPF exploitable, and should I be worried? Whether GHSA-9GHP-W2HM-VFPF 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-9GHP-W2HM-VFPF 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-9GHP-W2HM-VFPF? Upgrade wasmtime-jit-debug to 24.0.0 or later.