{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-25299 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-25299 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25299 is a critical path traversal vulnerability in Cesanta Mongoose, published on 18 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-25299 and fix it if it is affected.\n\nWhat it is: CVE-2022-25299 is a critical path traversal vulnerability in Cesanta Mongoose, published on 18 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-25299 in the wild and no public exploit code.\n\nAffected product: Cesanta Mongoose. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2022-25299/ (Markdown: https://insights.sbomify.com/CVE-2022-25299/index.md)","id":"CVE-2022-25299","markdown":"https://insights.sbomify.com/CVE-2022-25299/index.md","name":"CVE-2022-25299","record":{"aliases":["GHSA-q66h-r8q8-x284","SNYK-UNMANAGED-CESANTAMONGOOSE-2404180","UBUNTU-CVE-2022-25299"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Cesanta Mongoose library","requires_auth":"none","summary":"Attackers can write files to arbitrary locations outside the designated folder via unsafe filename handling in the upload method.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"mongoose","vendor":"cesanta"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-552","name":"Files or Directories Accessible to External Parties"}],"description":"This affects the package cesanta/mongoose before 7.6. The unsafe handling of file names during upload using mg_http_upload() method may enable attackers to write files to arbitrary locations outside the designated target folder.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Arbitrary File Write","id":"CVE-2022-25299","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"cesanta:mongoose","products":["cesanta:mongoose"],"type":"path_traversal","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Prototype Pollution","id":"CVE-2022-25301"},"packages":[],"prev":{"headline":"Path Traversal","id":"CVE-2022-25298"},"products":["cesanta/mongoose"],"published":"2022-02-18","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-25756","kev_date_added":null,"published":"2020-09-18"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2019-19307","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-12951","kev_date_added":null,"published":"2019-06-24"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2018-20353","kev_date_added":null,"published":"2019-06-10"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2018-20354","kev_date_added":null,"published":"2019-06-10"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2018-20355","kev_date_added":null,"published":"2019-06-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Attackers can write files to arbitrary locations outside the designated folder via unsafe filename handling in the upload method.","url":"https://insights.sbomify.com/CVE-2022-25299/"}