{"answers":{"affected":"2 open source packages ship an affected version, including wasmer-cli. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51661 exists.","fix":"Upgrade wasmer-cli to 4.2.4 or later.","what":"CVE-2023-51661 is a high-severity path traversal vulnerability in wasmerio wasmer, published on 22 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-51661 and fix it if it is affected.\n\nWhat it is: CVE-2023-51661 is a high-severity path traversal vulnerability in wasmerio wasmer, published on 22 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51661 exists.\n\nAffected packages and fixed versions:\n- wasmer-cli (crates.io): affected from 3.0.0; fixed in 4.2.4\n- wasmer-cli (crates.io): affected from 3.0.0; fixed in 4.2.4\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-51661/ (Markdown: https://insights.sbomify.com/CVE-2023-51661/index.md)","id":"CVE-2023-51661","markdown":"https://insights.sbomify.com/CVE-2023-51661/index.md","name":"CVE-2023-51661","record":{"aliases":["GHSA-4mq4-7rw3-vm5j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WebAssembly runtime","requires_auth":"none","summary":"Attackers can escape the filesystem sandbox to read or modify host files when running untrusted WebAssembly code.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wasmer","vendor":"wasmer"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"Wasmer is a WebAssembly runtime that enables containers to run anywhere: from Desktop to the Cloud, Edge and even the browser. Wasm programs can access the filesystem outside of the sandbox. Service providers running untrusted Wasm code on Wasmer can unexpectedly expose the host filesystem. This vulnerability has been patched in version 4.2.4.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Filesystem sandbox not enforced in wasmer-cli","id":"CVE-2023-51661","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":2,"n_references":3,"next":{"headline":"Snowflake Connector .NET does not properly check the Certificate Revocation List (CRL)","id":"CVE-2023-51662"},"packages":[{"ecosystem":"crates.io","fixed":["4.2.4"],"introduced":["3.0.0"],"last_affected":[],"package":"wasmer-cli","purl":null,"source":"GHSA-4mq4-7rw3-vm5j"},{"ecosystem":"crates.io","fixed":["4.2.4"],"introduced":["3.0.0"],"last_affected":[],"package":"wasmer-cli","purl":"pkg:cargo/wasmer-cli","source":"GHSA-4mq4-7rw3-vm5j"}],"prev":{"headline":"Apache IoTDB: Unsafe deserialize map in Sync Tool","id":"CVE-2023-51656"},"products":["wasmer"],"published":"2023-12-22","related":[],"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":"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-17","vendors":["wasmerio"]},"summary":"Attackers can escape the filesystem sandbox to read or modify host files when running untrusted WebAssembly code.","url":"https://insights.sbomify.com/CVE-2023-51661/"}