{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-38730 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-38730 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-38730 is a medium-severity vulnerability in n/a, published on 27 Apr 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-2022-38730 and fix it if it is affected.\n\nWhat it is: CVE-2022-38730 is a medium-severity vulnerability in n/a, published on 27 Apr 2023. 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-38730 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-38730/ (Markdown: https://insights.sbomify.com/CVE-2022-38730/index.md)","id":"CVE-2022-38730","markdown":"https://insights.sbomify.com/CVE-2022-38730/index.md","name":"CVE-2022-38730","record":{"aliases":["GHSA-pmgh-8j9v-4xhf"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Docker Desktop","requires_auth":"low_privilege","summary":"Attackers can overwrite arbitrary files via a TOCTOU race condition in Docker Desktop for Windows, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"desktop","vendor":"docker"}],"cvss":{"score":6.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"},{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Docker Desktop for Windows before 4.6 allows attackers to overwrite any file through the windowscontainers/start dockerBackendV2 API by controlling the data-root field inside the DaemonJSON field in the WindowsContainerStartRequest class. This allows exploiting a symlink vulnerability in ..\\dataRoot\\network\\files\\local-kv.db because of a TOCTOU race condition.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Race condition in n/a","id":"CVE-2022-38730","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2022-38731"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2022-38725"},"products":["n/a"],"published":"2023-04-27","related":[{"cvss_score":9,"headline":"Code injection in Docker Desktop","id":"CVE-2024-8695","kev_date_added":null,"published":"2024-09-12"},{"cvss_score":8.9,"headline":"Code injection in Docker Desktop","id":"CVE-2024-8696","kev_date_added":null,"published":"2024-09-12"},{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2022-37326","kev_date_added":null,"published":"2023-04-27"},{"cvss_score":7.8,"headline":"Missing authorization in n/a","id":"CVE-2021-37841","kev_date_added":null,"published":"2021-08-12"},{"cvss_score":7.3,"headline":"Elevation of Privilege in Docker Desktop for Windows during Upgrade due to Insecure Directory Deletion","id":"CVE-2025-3224","kev_date_added":null,"published":"2025-04-28"},{"cvss_score":7.3,"headline":"Privilege escalation in Docker Desktop","id":"CVE-2024-6222","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":7.1,"headline":"Docker Desktop before 4.6.0 on Windows allows attackers to delete any file through the hyperv/destroy dockerBackendV2 API via a symlink in t","id":"CVE-2022-31647","kev_date_added":null,"published":"2023-04-27"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-31","vendors":["n/a"]},"summary":"Attackers can overwrite arbitrary files via a TOCTOU race condition in Docker Desktop for Windows, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2022-38730/"}