{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15360 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15360 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15360 is a high-severity missing authorization vulnerability in n/a, published on 27 Jun 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-15360 and fix it if it is affected.\n\nWhat it is: CVE-2020-15360 is a high-severity missing authorization vulnerability in n/a, published on 27 Jun 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-15360 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-15360/ (Markdown: https://insights.sbomify.com/CVE-2020-15360/index.md)","id":"CVE-2020-15360","markdown":"https://insights.sbomify.com/CVE-2020-15360/index.md","name":"CVE-2020-15360","record":{"aliases":["GHSA-wg4x-5mmv-p8gp"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Docker Desktop","requires_auth":"low_privilege","summary":"Attackers can escalate privileges on Docker Desktop due to missing client verification in the vmnetd service.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"docker_desktop","vendor":"docker"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"com.docker.vmnetd in Docker Desktop 2.3.0.3 allows privilege escalation because of a lack of client verification.","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":"Missing authorization in n/a","id":"CVE-2020-15360","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"OS Command Injection in wifiscanner","id":"CVE-2020-15362"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-15358"},"products":["n/a"],"published":"2020-06-27","related":[{"cvss_score":8.8,"headline":"Docker Model Runner container-to-host code execution via unsandboxed trust_remote_code in Python inference backends","id":"CVE-2026-5817","kev_date_added":null,"published":"2026-05-22"},{"cvss_score":8.8,"headline":"Docker Model Runner container-to-host code execution via MLX-LM model_file importlib loading","id":"CVE-2026-5843","kev_date_added":null,"published":"2026-05-22"},{"cvss_score":8.8,"headline":"Docker Desktop Enhanced Container Isolation bypass via --use-api-socket CLI flag","id":"CVE-2026-6406","kev_date_added":null,"published":"2026-05-22"},{"cvss_score":8.4,"headline":"Missing authorization in n/a","id":"CVE-2021-44719","kev_date_added":null,"published":"2022-05-25"},{"cvss_score":8,"headline":"Docker Desktop before 4.12.0 is vulnerable to RCE via a crafted extension description or changelog","id":"CVE-2023-0625","kev_date_added":null,"published":"2023-09-25"},{"cvss_score":8,"headline":"Docker Desktop before 4.12.0 is vulnerable to RCE via query parameters in message-box route","id":"CVE-2023-0626","kev_date_added":null,"published":"2023-09-25"},{"cvss_score":8,"headline":"Docker Desktop before 4.23.0 allows Access Token theft via a crafted extension icon URL","id":"CVE-2023-5166","kev_date_added":null,"published":"2023-09-25"}],"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-08-04","vendors":["n/a"]},"summary":"Attackers can escalate privileges on Docker Desktop due to missing client verification in the vmnetd service.","url":"https://insights.sbomify.com/CVE-2020-15360/"}