{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10665 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10665 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10665 is a medium-severity vulnerability in n/a, published on 18 Mar 2020. 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-2020-10665 and fix it if it is affected.\n\nWhat it is: CVE-2020-10665 is a medium-severity vulnerability in n/a, published on 18 Mar 2020. 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-2020-10665 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-2020-10665/ (Markdown: https://insights.sbomify.com/CVE-2020-10665/index.md)","id":"CVE-2020-10665","markdown":"https://insights.sbomify.com/CVE-2020-10665/index.md","name":"CVE-2020-10665","record":{"aliases":["GHSA-22mx-2pf3-v75r"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Docker Desktop","requires_auth":"high_privilege","summary":"Local attackers can escalate privileges to SYSTEM via arbitrary file writes during diagnostics collection in Docker Desktop for Windows.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"desktop","vendor":"docker"}],"cvss":{"score":6.7,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Docker Desktop allows local privilege escalation to NT AUTHORITY\\SYSTEM because it mishandles the collection of diagnostics with Administrator privileges, leading to arbitrary DACL permissions overwrites and arbitrary file writes. This affects Docker Desktop Enterprise before 2.1.0.9, Docker Desktop for Windows Stable before 2.2.0.4, and Docker Desktop for Windows Edge before 2.2.2.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-06-25","github_poc":1,"max_poc_stars":52,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-06-25T07:35:29Z","kind":"github_poc","ref":"https://github.com/spaceraccoon/CVE-2020-10665","stars":52,"title":"POC for CVE-2020-10665 Docker Desktop Local Privilege Escalation"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2020-10665","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2020-10666"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2020-10664"},"products":["n/a"],"published":"2020-03-18","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Local attackers can escalate privileges to SYSTEM via arbitrary file writes during diagnostics collection in Docker Desktop for Windows.","url":"https://insights.sbomify.com/CVE-2020-10665/"}