{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-6222 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-6222 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-6222 is a high-severity vulnerability in Docker Desktop, published on 9 Jul 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-6222 and fix it if it is affected.\n\nWhat it is: CVE-2024-6222 is a high-severity vulnerability in Docker Desktop, published on 9 Jul 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-6222 in the wild and no public exploit code.\n\nAffected product: Docker Desktop. 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-2024-6222/ (Markdown: https://insights.sbomify.com/CVE-2024-6222/index.md)","id":"CVE-2024-6222","markdown":"https://insights.sbomify.com/CVE-2024-6222/index.md","name":"CVE-2024-6222","record":{"aliases":["GHSA-77gv-24g3-732h"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Docker Desktop","requires_auth":"high_privilege","summary":"Attackers escaping a container can break out to the host via IPC messages if marketplace restrictions are disabled, requiring an upgrade to Docker Desktop.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Docker","cpe":[{"product":"desktop","vendor":"docker"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-923","name":"Improper Restriction of Communication Channel to Intended Endpoints"}],"description":"In Docker Desktop before v4.29.0, an attacker who has gained access to the Docker Desktop VM through a container breakout can further escape to the host by passing extensions and dashboard related IPC messages.\n\nDocker Desktop  v4.29.0 https://docs.docker.com/desktop/release-notes/#4290  fixes the issue on MacOS, Linux and Windows with Hyper-V backend.\n\nAs exploitation requires \"Allow only extensions distributed through the Docker Marketplace\" to be disabled, Docker Desktop  v4.31.0 https://docs.docker.com/desktop/release-notes/#4310  additionally changes the default configuration to enable this setting by default.","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":"Privilege escalation in Docker Desktop","id":"CVE-2024-6222","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Send email only on Reply to My Comment \u003c= 1.0.6 - Reflected XSS","id":"CVE-2024-6223"},"packages":[],"prev":{"headline":"Improper Access Control in corydolphin/flask-cors","id":"CVE-2024-6221"},"products":["Docker Desktop"],"published":"2024-07-09","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.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":"2024-08-01","vendors":["Docker Inc."]},"summary":"Attackers escaping a container can break out to the host via IPC messages if marketplace restrictions are disabled, requiring an upgrade to Docker Desktop.","url":"https://insights.sbomify.com/CVE-2024-6222/"}