{"answers":{"affected":"2 open source packages ship an affected version, including wasmer.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-38358 exists.","fix":"No fix has been published for CVE-2024-38358 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-38358 is a low-severity path traversal vulnerability in wasmerio wasmer, published on 19 Jun 2024. 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-2024-38358 and fix it if it is affected.\n\nWhat it is: CVE-2024-38358 is a low-severity path traversal vulnerability in wasmerio wasmer, published on 19 Jun 2024. 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-2024-38358 exists.\n\nAffected packages and fixed versions:\n- wasmer (crates.io): affected all versions up to 4.3.1; no fix listed\n- wasmer (crates.io): affected all versions up to 4.3.1; no fix listed\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-38358/ (Markdown: https://insights.sbomify.com/CVE-2024-38358/index.md)","id":"CVE-2024-38358","markdown":"https://insights.sbomify.com/CVE-2024-38358/index.md","name":"CVE-2024-38358","record":{"aliases":["GHSA-55f3-3qvg-8pv5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"WebAssembly runtime","requires_auth":"none","summary":"A symlink bypass in the Wasmer runtime allows WASI programs to access the host filesystem or crash the runtime if specific flags are set.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.9,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Wasmer is a web assembly (wasm) Runtime supporting WASIX, WASI and Emscripten. If the preopened directory has a symlink pointing outside, WASI programs can traverse the symlink and access host filesystem if the caller sets both `oflags::creat` and `rights::fd_write`. Programs can also crash the runtime by creating a symlink pointing outside with `path_symlink` and `path_open`ing the link. This issue has been addressed in commit `b9483d022` which has been included in release version 4.3.2. Users are advised to upgrade. There are no known workarounds for this vulnerability.","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":false,"headline":"Symlink bypasses filesystem sandbox in wasmer","id":"CVE-2024-38358","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"Lightning Network Daemon Onion Bomb","id":"CVE-2024-38359"},"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["4.3.1"],"package":"wasmer","purl":null,"source":"GHSA-55f3-3qvg-8pv5"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["4.3.1"],"package":"wasmer","purl":"pkg:cargo/wasmer","source":"GHSA-55f3-3qvg-8pv5"}],"prev":{"headline":"TinyMCE Cross-Site Scripting (XSS) vulnerability using noscript elements","id":"CVE-2024-38357"},"products":["wasmer"],"published":"2024-06-19","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["wasmerio"]},"summary":"A symlink bypass in the Wasmer runtime allows WASI programs to access the host filesystem or crash the runtime if specific flags are set.","url":"https://insights.sbomify.com/CVE-2024-38358/"}