{"answers":{"affected":"7 open source packages ship an affected version, including wasmtime. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-30624 in the wild and no public exploit code.","fix":"Upgrade wasmtime to a fixed version for your release line: 6.0.2, 7.0.1 or 8.0.1.","what":"CVE-2023-30624 is a low-severity memory corruption vulnerability in bytecodealliance wasmtime, published on 27 Apr 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-30624 and fix it if it is affected.\n\nWhat it is: CVE-2023-30624 is a low-severity memory corruption vulnerability in bytecodealliance wasmtime, published on 27 Apr 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-30624 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- wasmtime (crates.io): affected all versions; fixed in 6.0.2\n- wasmtime (crates.io): affected all versions; fixed in 6.0.2\n- wasmtime (crates.io): affected from 0.0.0-0; fixed in 6.0.2, 7.0.1, 8.0.1\n- wasmtime (crates.io): affected from 7.0.0; fixed in 7.0.1\n- wasmtime (crates.io): affected from 7.0.0; fixed in 7.0.1\n- wasmtime (crates.io): affected from 8.0.0; fixed in 8.0.1\n- wasmtime (crates.io): affected from 8.0.0; fixed in 8.0.1\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/CVE-2023-30624/ (Markdown: https://insights.sbomify.com/CVE-2023-30624/index.md)","id":"CVE-2023-30624","markdown":"https://insights.sbomify.com/CVE-2023-30624/index.md","name":"CVE-2023-30624","record":{"aliases":["GHSA-ch89-5g45-qwc7","RUSTSEC-2023-0092"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"WebAssembly runtime","requires_auth":"high_privilege","summary":"Undefined behavior in Wasmtime's unsafe Rust code can lead to memory corruption and potential code execution when compiled with specific LLVM versions.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wasmtime","vendor":"bytecodealliance"}],"cvss":{"score":3.9,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-758","name":"Reliance on Undefined, Unspecified, or Implementation-Defined Behavior"}],"description":"Wasmtime is a standalone runtime for WebAssembly. Prior to versions 6.0.2, 7.0.1, and 8.0.1, Wasmtime's implementation of managing per-instance state, such as tables and memories, contains LLVM-level undefined behavior. This undefined behavior was found to cause runtime-level issues when compiled with LLVM 16 which causes some writes, which are critical for correctness, to be optimized away. Vulnerable versions of Wasmtime compiled with Rust 1.70, which is currently in beta, or later are known to have incorrectly compiled functions. Versions of Wasmtime compiled with the current Rust stable release, 1.69, and prior are not known at this time to have any issues, but can theoretically exhibit potential issues.\n\nThe underlying problem is that Wasmtime's runtime state for an instance involves a Rust-defined structure called `Instance` which has a trailing `VMContext` structure after it. This `VMContext` structure has a runtime-defined layout that is unique per-module. This representation cannot be expressed with safe code in Rust so `unsafe` code is required to maintain this state. The code doing this, however, has methods which take `\u0026self` as an argument but modify data in the `VMContext` part of the allocation. This means that pointers derived from `\u0026self` are mutated. This is typically not allowed, except in the presence of `UnsafeCell`, in Rust. When compiled to LLVM these functions have `noalias readonly` parameters which means it's UB to write through the pointers.\n\nWasmtime's internal representation and management of `VMContext` has been updated to use `\u0026mut self` methods where appropriate. Additionally verification tools for `unsafe` code in Rust, such as `cargo miri`, are planned to be executed on the `main` branch soon to fix any Rust-level issues that may be exploited in future compiler versions.\n\nPrecomplied binaries available for Wasmtime from GitHub releases have been compiled with at most LLVM 15 so are not known to be vulnerable. As mentioned above, however, it's still recommended to update.\n\nWasmtime version 6.0.2, 7.0.1, and 8.0.1 have been issued which contain the patch necessary to work correctly on LLVM 16 and have no known UB on LLVM 15 and earlier. If Wasmtime is compiled with Rust 1.69 and prior, which use LLVM 15, then there are no known issues. There is a theoretical possibility for undefined behavior to exploited, however, so it's recommended that users upgrade to a patched version of Wasmtime. Users using beta Rust (1.70 at this time) or nightly Rust (1.71 at this time) must update to a patched version to work correctly.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Wasmtime has Undefined Behavior in Rust runtime functions","id":"CVE-2023-30624","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":7,"n_references":2,"next":{"headline":"rudder-server vulnerable to SQL Injection","id":"CVE-2023-30625"},"packages":[{"ecosystem":"crates.io","fixed":["6.0.2"],"introduced":["0"],"last_affected":[],"package":"wasmtime","purl":null,"source":"GHSA-ch89-5g45-qwc7"},{"ecosystem":"crates.io","fixed":["6.0.2"],"introduced":["0"],"last_affected":[],"package":"wasmtime","purl":"pkg:cargo/wasmtime","source":"GHSA-ch89-5g45-qwc7"},{"ecosystem":"crates.io","fixed":["6.0.2","7.0.1","8.0.1"],"introduced":["0.0.0-0","7.0.0","8.0.0"],"last_affected":[],"package":"wasmtime","purl":"pkg:cargo/wasmtime","source":"RUSTSEC-2023-0092"},{"ecosystem":"crates.io","fixed":["7.0.1"],"introduced":["7.0.0"],"last_affected":[],"package":"wasmtime","purl":null,"source":"GHSA-ch89-5g45-qwc7"},{"ecosystem":"crates.io","fixed":["7.0.1"],"introduced":["7.0.0"],"last_affected":[],"package":"wasmtime","purl":"pkg:cargo/wasmtime","source":"GHSA-ch89-5g45-qwc7"},{"ecosystem":"crates.io","fixed":["8.0.1"],"introduced":["8.0.0"],"last_affected":[],"package":"wasmtime","purl":null,"source":"GHSA-ch89-5g45-qwc7"},{"ecosystem":"crates.io","fixed":["8.0.1"],"introduced":["8.0.0"],"last_affected":[],"package":"wasmtime","purl":"pkg:cargo/wasmtime","source":"GHSA-ch89-5g45-qwc7"}],"prev":{"headline":"Arbitrary command injection in embano1/wip","id":"CVE-2023-30623"},"products":["wasmtime"],"published":"2023-04-27","related":[{"cvss_score":9,"headline":"Wasmtime miscompiled guest heap access enables sandbox escape on aarch64 Cranelift","id":"CVE-2026-34971","kev_date_added":null,"published":"2026-04-09"},{"cvss_score":9,"headline":"Wasmtime with Winch compiler backend on aarch64 may allow a sandbox-escaping memory access","id":"CVE-2026-34987","kev_date_added":null,"published":"2026-04-09"},{"cvss_score":8.6,"headline":"Wasmtime vulnerable to data leakage between instances in the pooling allocator","id":"CVE-2022-39393","kev_date_added":null,"published":"2022-11-10"},{"cvss_score":8.1,"headline":"Use after free in Wasmtime","id":"CVE-2022-24791","kev_date_added":null,"published":"2022-03-31"},{"cvss_score":7.5,"headline":"Wasmtime: WASI path_open(TRUNCATE) bypasses `FilePerms::WRITE` host restriction","id":"CVE-2026-47261","kev_date_added":null,"published":"2026-06-15"},{"cvss_score":6.9,"headline":"Wasmtime has a Heap OOB read in component model UTF-16 to latin1+utf16 string transcoding","id":"CVE-2026-34941","kev_date_added":null,"published":"2026-04-09"},{"cvss_score":6.9,"headline":"Wasmtime is vulnerable to panic when dropping a `[Typed]Func::call_async` future","id":"CVE-2026-27195","kev_date_added":null,"published":"2026-02-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-30","vendors":["bytecodealliance"]},"summary":"Undefined behavior in Wasmtime's unsafe Rust code can lead to memory corruption and potential code execution when compiled with specific LLVM versions.","url":"https://insights.sbomify.com/CVE-2023-30624/"}