{"answers":{"affected":"3 open source packages ship an affected version, including wasmtime-jit-debug.","exploited":"There is no known exploitation of GHSA-9ghp-w2hm-vfpf in the wild and no public exploit code.","fix":"Upgrade wasmtime-jit-debug to 24.0.0 or later.","what":"GHSA-9ghp-w2hm-vfpf is a vulnerability in wasmtime-jit-debug, published on 6 Jul 2024."},"fix_prompt":"Check this codebase for GHSA-9ghp-w2hm-vfpf and fix it if it is affected.\n\nWhat it is: GHSA-9ghp-w2hm-vfpf is a vulnerability in wasmtime-jit-debug, published on 6 Jul 2024. \nExploitation: There is no known exploitation of GHSA-9ghp-w2hm-vfpf in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- wasmtime-jit-debug (crates.io): affected all versions; fixed in 24.0.0\n- wasmtime-jit-debug (crates.io): affected all versions; fixed in 24.0.0\n- wasmtime-jit-debug (crates.io): affected from 0.0.0-0; fixed in 24.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-9ghp-w2hm-vfpf/ (Markdown: https://insights.sbomify.com/GHSA-9ghp-w2hm-vfpf/index.md)","id":"GHSA-9ghp-w2hm-vfpf","markdown":"https://insights.sbomify.com/GHSA-9ghp-w2hm-vfpf/index.md","name":"GHSA-9ghp-w2hm-vfpf","record":{"aliases":["RUSTSEC-2024-0442"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"unknown","non_default_config":false,"product_category":"Wasmtime JIT dump crate","requires_auth":"none","summary":"An internal Wasmtime crate allows dumping undefined memory to a file due to unsound pointer handling, potentially leaking sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The unsound function `dump_code_load_record` uses `from_raw_parts` to directly convert \nthe pointer `addr` and `len` into a slice without any validation and that memory block \nwould be dumped.\n\nThus, the 'safe' function dump_code_load_record is actually 'unsafe' since it requires \nthe caller to guarantee that the addr is valid and len must not overflow.\nOtherwise, the function could dump the memory into file illegally, causing memory leak.\n\n\u003e **Note**: this is an internal-only crate in the Wasmtime project not intended for\nexternal use and is more strongly signaled nowadays as of\n[bytecodealliance/wasmtime#10963](https://github.com/bytecodealliance/wasmtime/pull/10963).\nPlease open an issue in Wasmtime if you're using this crate directly.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Dump Undefined Memory by `JitDumpFile`","id":"GHSA-9ghp-w2hm-vfpf","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["24.0.0"],"introduced":["0"],"last_affected":[],"package":"wasmtime-jit-debug","purl":null,"source":"GHSA-9ghp-w2hm-vfpf"},{"ecosystem":"crates.io","fixed":["24.0.0"],"introduced":["0"],"last_affected":[],"package":"wasmtime-jit-debug","purl":"pkg:cargo/wasmtime-jit-debug","source":"GHSA-9ghp-w2hm-vfpf"},{"ecosystem":"crates.io","fixed":["24.0.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"wasmtime-jit-debug","purl":"pkg:cargo/wasmtime-jit-debug","source":"RUSTSEC-2024-0442"}],"products":null,"published":"2024-07-06","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An internal Wasmtime crate allows dumping undefined memory to a file due to unsound pointer handling, potentially leaking sensitive data.","url":"https://insights.sbomify.com/GHSA-9ghp-w2hm-vfpf/"}