{"answers":{"affected":"2 open source packages ship an affected version, including @saltcorn/server.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47818 exists.","fix":"Upgrade @saltcorn/server to 1.0.0-beta.16 or later.","what":"CVE-2024-47818 is a medium-severity path traversal vulnerability in saltcorn, published on 7 Oct 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-47818 and fix it if it is affected.\n\nWhat it is: CVE-2024-47818 is a medium-severity path traversal vulnerability in saltcorn, published on 7 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47818 exists.\n\nAffected packages and fixed versions:\n- @saltcorn/server (npm): affected all versions; fixed in 1.0.0-beta.16\n- @saltcorn/server (npm): affected all versions; fixed in 1.0.0-beta.16\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-47818/ (Markdown: https://insights.sbomify.com/CVE-2024-47818/index.md)","id":"CVE-2024-47818","markdown":"https://insights.sbomify.com/CVE-2024-47818/index.md","name":"CVE-2024-47818","record":{"aliases":["GHSA-43f3-h63w-p6f6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Saltcorn server","requires_auth":"low_privilege","summary":"Logged-in users can delete arbitrary files on the server via an unvalidated parameter in the sync directory cleanup endpoint.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Saltcorn is an extensible, open source, no-code database application builder. A logged-in user with any role can delete arbitrary files on the filesystem by calling the `sync/clean_sync_dir` endpoint. The `dir_name` POST parameter is not validated/sanitized and is used to construct the `syncDir` that is deleted by calling `fs.rm`. This issue has been addressed in release version 1.0.0-beta16 and all users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Logged-in users with any role can delete arbitrary files in @saltcorn/server","id":"CVE-2024-47818","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"Umbraco CMS vulnerable to stored Cross-site Scripting in the \"dictionary name\" on Dictionary section","id":"CVE-2024-47819"},"packages":[{"ecosystem":"npm","fixed":["1.0.0-beta.16"],"introduced":["0"],"last_affected":[],"package":"@saltcorn/server","purl":null,"source":"GHSA-43f3-h63w-p6f6"},{"ecosystem":"npm","fixed":["1.0.0-beta.16"],"introduced":["0"],"last_affected":[],"package":"@saltcorn/server","purl":"pkg:npm/%40saltcorn/server","source":"GHSA-43f3-h63w-p6f6"}],"prev":{"headline":"Unvalidated paragraph widget values can be used for Cross-site Scripting in lara-zeus","id":"CVE-2024-47817"},"products":["saltcorn"],"published":"2024-10-07","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-10-08","vendors":["saltcorn"]},"summary":"Logged-in users can delete arbitrary files on the server via an unvalidated parameter in the sync directory cleanup endpoint.","url":"https://insights.sbomify.com/CVE-2024-47818/"}