{"answers":{"affected":"7 open source packages ship an affected version, including wasmtime. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-51745 in the wild and no public exploit code.","fix":"Upgrade wasmtime to a fixed version for your release line: 24.0.2, 25.0.3 or 26.0.1.","what":"CVE-2024-51745 is a low-severity vulnerability in bytecodealliance wasmtime, published on 5 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-51745 and fix it if it is affected.\n\nWhat it is: CVE-2024-51745 is a low-severity vulnerability in bytecodealliance wasmtime, published on 5 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-51745 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- wasmtime (crates.io): affected all versions; fixed in 24.0.2\n- wasmtime (crates.io): affected all versions; fixed in 24.0.2\n- wasmtime (crates.io): affected from 0.0.0-0; fixed in 24.0.2, 25.0.3, 26.0.1\n- wasmtime (crates.io): affected from 25.0.0; fixed in 25.0.3\n- wasmtime (crates.io): affected from 25.0.0; fixed in 25.0.3\n- wasmtime (crates.io): affected from 26.0.0; fixed in 26.0.1\n- wasmtime (crates.io): affected from 26.0.0; fixed in 26.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-2024-51745/ (Markdown: https://insights.sbomify.com/CVE-2024-51745/index.md)","id":"CVE-2024-51745","markdown":"https://insights.sbomify.com/CVE-2024-51745/index.md","name":"CVE-2024-51745","record":{"aliases":["DEBIAN-CVE-2024-51745","GHSA-c2f5-jxjv-2hh8","JLSEC-2026-1348","RUSTSEC-2024-0438"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WebAssembly runtime","requires_auth":"low_privilege","summary":"Untrusted WebAssembly programs can bypass filesystem sandboxing on Windows to access serial and parallel devices via superscript filenames.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wasmtime","vendor":"bytecodealliance"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-67","name":"Improper Handling of Windows Device Names"},{"id":"CWE-184","name":"Incomplete List of Disallowed Inputs"}],"description":"Wasmtime is a fast and secure runtime for WebAssembly. Wasmtime's filesystem sandbox implementation on Windows blocks access to special device filenames such as \"COM1\", \"COM2\", \"LPT0\", \"LPT1\", and so on, however it did not block access to the special device filenames which use superscript digits, such as \"COM¹\", \"COM²\", \"LPT⁰\", \"LPT¹\", and so on. Untrusted Wasm programs that are given access to any filesystem directory could bypass the sandbox and access devices through those special device filenames with superscript digits, and through them gain access peripheral devices connected to the computer, or network resources mapped to those devices. This can include modems, printers, network printers, and any other device connected to a serial or parallel port, including emulated USB serial ports. Patch releases for Wasmtime have been issued as 24.0.2, 25.0.3, and 26.0.1. Users of Wasmtime 23.0.x and prior are recommended to upgrade to one of these patched versions. There are no known workarounds for this issue. Affected Windows users are recommended to upgrade.","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 doesn't fully sandbox all the Windows device filenames","id":"CVE-2024-51745","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":7,"n_references":4,"next":{"headline":"Use of incorrect Rekor entries during verification in gitsign","id":"CVE-2024-51746"},"packages":[{"ecosystem":"crates.io","fixed":["24.0.2"],"introduced":["0"],"last_affected":[],"package":"wasmtime","purl":null,"source":"GHSA-c2f5-jxjv-2hh8"},{"ecosystem":"crates.io","fixed":["24.0.2"],"introduced":["0"],"last_affected":[],"package":"wasmtime","purl":"pkg:cargo/wasmtime","source":"GHSA-c2f5-jxjv-2hh8"},{"ecosystem":"crates.io","fixed":["24.0.2","25.0.3","26.0.1"],"introduced":["0.0.0-0","25.0.0","26.0.0"],"last_affected":[],"package":"wasmtime","purl":"pkg:cargo/wasmtime","source":"RUSTSEC-2024-0438"},{"ecosystem":"crates.io","fixed":["25.0.3"],"introduced":["25.0.0"],"last_affected":[],"package":"wasmtime","purl":null,"source":"GHSA-c2f5-jxjv-2hh8"},{"ecosystem":"crates.io","fixed":["25.0.3"],"introduced":["25.0.0"],"last_affected":[],"package":"wasmtime","purl":"pkg:cargo/wasmtime","source":"GHSA-c2f5-jxjv-2hh8"},{"ecosystem":"crates.io","fixed":["26.0.1"],"introduced":["26.0.0"],"last_affected":[],"package":"wasmtime","purl":null,"source":"GHSA-c2f5-jxjv-2hh8"},{"ecosystem":"crates.io","fixed":["26.0.1"],"introduced":["26.0.0"],"last_affected":[],"package":"wasmtime","purl":"pkg:cargo/wasmtime","source":"GHSA-c2f5-jxjv-2hh8"}],"prev":{"headline":"Bad documentation of error handling in ParseWithClaims can lead to potentially dangerous situations in golang-jwt","id":"CVE-2024-51744"},"products":["wasmtime"],"published":"2024-11-05","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":"2024-11-05","vendors":["bytecodealliance"]},"summary":"Untrusted WebAssembly programs can bypass filesystem sandboxing on Windows to access serial and parallel devices via superscript filenames.","url":"https://insights.sbomify.com/CVE-2024-51745/"}