{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-25365 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-25365 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25365 is a high-severity path traversal vulnerability in n/a, published on 19 Feb 2022. 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-2022-25365 and fix it if it is affected.\n\nWhat it is: CVE-2022-25365 is a high-severity path traversal vulnerability in n/a, published on 19 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-25365 in the wild and no public exploit code.\n\nAffected product: n/a. 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-25365/ (Markdown: https://insights.sbomify.com/CVE-2022-25365/index.md)","id":"CVE-2022-25365","markdown":"https://insights.sbomify.com/CVE-2022-25365/index.md","name":"CVE-2022-25365","record":{"aliases":["GHSA-hj5h-vmcf-v2w4"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_modify","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Docker Desktop","requires_auth":"low_privilege","summary":"Attackers can move arbitrary files on Windows systems using Docker Desktop, potentially leading to privilege escalation or data modification.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"docker","vendor":"docker"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:L/AV:L/A:H/C:H/I:H/PR:L/S:U/UI:N","version":"3.1"},"cwes":[],"description":"Docker Desktop before 4.5.1 on Windows allows attackers to move arbitrary files. NOTE: this issue exists because of an incomplete fix for CVE-2022-23774.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2023-02-19","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-02-19T13:19:10Z","kind":"github_poc","ref":"https://github.com/followboy1999/CVE-2022-25365","stars":1,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"Path traversal in n/a","id":"CVE-2022-25365","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in n/a","id":"CVE-2022-25366"},"packages":[],"prev":{"headline":"Misconfiguration in n/a","id":"CVE-2022-25364"},"products":["n/a"],"published":"2022-02-19","related":[{"cvss_score":10,"headline":"Arbitrary Code Execution","id":"CVE-2014-9357","kev_date_added":null,"published":"2014-12-16"},{"cvss_score":8.8,"headline":"Privilege escalation in Docker","id":"CVE-2020-14298","kev_date_added":null,"published":"2020-07-13"},{"cvss_score":8.8,"headline":"Privilege escalation in Docker","id":"CVE-2020-14300","kev_date_added":null,"published":"2020-07-13"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2018-15514","kev_date_added":null,"published":"2018-09-01"},{"cvss_score":8.6,"headline":"Path Traversal in Docker","id":"CVE-2014-9356","kev_date_added":null,"published":"2019-12-02"},{"cvss_score":8.4,"headline":"Command injection in n/a","id":"CVE-2019-13139","kev_date_added":null,"published":"2019-08-22"},{"cvss_score":8.1,"headline":"Other in n/a","id":"CVE-2014-5282","kev_date_added":null,"published":"2018-02-06"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can move arbitrary files on Windows systems using Docker Desktop, potentially leading to privilege escalation or data modification.","url":"https://insights.sbomify.com/CVE-2022-25365/"}