{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-0629 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-0629 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-0629 is a high-severity vulnerability in Docker Desktop, published on 13 Mar 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-2023-0629 and fix it if it is affected.\n\nWhat it is: CVE-2023-0629 is a high-severity vulnerability in Docker Desktop, published on 13 Mar 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-2023-0629 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-2023-0629/ (Markdown: https://insights.sbomify.com/CVE-2023-0629/index.md)","id":"CVE-2023-0629","markdown":"https://insights.sbomify.com/CVE-2023-0629/index.md","name":"CVE-2023-0629","record":{"aliases":["GHSA-623v-x3rr-q8qh"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Docker Desktop","requires_auth":"low_privilege","summary":"Unprivileged users can bypass Enhanced Container Isolation restrictions by accessing the raw Docker socket to launch privileged containers.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Docker","cpe":[{"product":"docker_desktop","vendor":"docker"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-501","name":"Trust Boundary Violation"},{"id":"CWE-424","name":"Improper Protection of Alternate Path"}],"description":"Docker Desktop before 4.17.0 allows an unprivileged user to bypass Enhanced Container Isolation (ECI) restrictions by setting the Docker host to docker.raw.sock, or npipe:////.pipe/docker_engine_linux on Windows, via the -H (--host) CLI flag or the DOCKER_HOST environment variable and launch containers without the additional hardening features provided by ECI. This would not affect already running containers, nor containers launched through the usual approach (without Docker's raw socket).\n\nThe affected functionality is available for Docker Business customers only and assumes an environment where users are not granted local root or Administrator privileges.\nThis issue has been fixed in Docker Desktop 4.17.0. \n\nAffected Docker Desktop versions: from 4.13.0 before 4.17.0.","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":"Security feature bypass in Docker Desktop","id":"CVE-2023-0629","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Slimstat Analytics \u003c 4.9.3.3 - Subscriber+ SQL Injection","id":"CVE-2023-0630"},"packages":[],"prev":{"headline":"Command injection in Docker Desktop","id":"CVE-2023-0628"},"products":["Docker Desktop"],"published":"2023-03-13","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-27","vendors":["Docker Inc."]},"summary":"Unprivileged users can bypass Enhanced Container Isolation restrictions by accessing the raw Docker socket to launch privileged containers.","url":"https://insights.sbomify.com/CVE-2023-0629/"}