{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39206 exists.","fix":"No fix has been published for CVE-2022-39206 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-39206 is a critical vulnerability in theonedev onedev, published on 13 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-39206 and fix it if it is affected.\n\nWhat it is: CVE-2022-39206 is a critical vulnerability in theonedev onedev, published on 13 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39206 exists.\n\nAffected product: theonedev onedev. 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-39206/ (Markdown: https://insights.sbomify.com/CVE-2022-39206/index.md)","id":"CVE-2022-39206","markdown":"https://insights.sbomify.com/CVE-2022-39206/index.md","name":"CVE-2022-39206","record":{"aliases":["GHSA-gjq9-4xx9-cr3q"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Git server CI/CD","requires_auth":"low_privilege","summary":"Regular users can escape Docker containers to gain root privileges on the host by leveraging mounted Docker sockets in CI/CD jobs.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"onedev","vendor":"onedev_project"}],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-610","name":"Externally Controlled Reference to a Resource in Another Sphere"}],"description":"Onedev is an open source, self-hosted Git Server with CI/CD and Kanban. When using Docker-based job executors, the Docker socket (e.g. /var/run/docker.sock on Linux) is mounted into each Docker step. Users that can define and trigger CI/CD jobs on a project could use this to control the Docker daemon on the host machine. This is a known dangerous pattern, as it can be used to break out of Docker containers and, in most cases, gain root privileges on the host system. This issue allows regular (non-admin) users to potentially take over the build infrastructure of a OneDev instance. Attackers need to have an account (or be able to register one) and need permission to create a project. Since code.onedev.io has the right preconditions for this to be exploited by remote attackers, it could have been used to hijack builds of OneDev itself, e.g. by injecting malware into the docker images that are built and pushed to Docker Hub. The impact is increased by this as described before. Users are advised to upgrade to 7.3.0 or higher. There are no known workarounds for this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"CI/CD Docker Escape in OneDev","id":"CVE-2022-39206","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Persistent XSS in OneDev","id":"CVE-2022-39207"},"packages":[],"prev":{"headline":"Access Control Bypass in Onedev","id":"CVE-2022-39205"},"products":["onedev"],"published":"2022-09-13","related":[{"cvss_score":10,"headline":"Pre-Auth Unsafe Deserialization on AttachmentUploadServet","id":"CVE-2021-21242","kev_date_added":null,"published":"2021-01-15"},{"cvss_score":10,"headline":"Pre-Auth Unsafe Deserialization on KubernetesResource","id":"CVE-2021-21243","kev_date_added":null,"published":"2021-01-15"},{"cvss_score":10,"headline":"Pre-Auth SSTI via Bean validation message tampering","id":"CVE-2021-21244","kev_date_added":null,"published":"2021-01-15"},{"cvss_score":10,"headline":"Pre-Auth Arbitrary File Upload","id":"CVE-2021-21245","kev_date_added":null,"published":"2021-01-15"},{"cvss_score":9.6,"headline":"Post-Auth Unsafe Deserialization on BasePage (AJAX)","id":"CVE-2021-21247","kev_date_added":null,"published":"2021-01-15"},{"cvss_score":9.6,"headline":"Post-Auth Arbitrary Code execution via Groovy script injection","id":"CVE-2021-21248","kev_date_added":null,"published":"2021-01-15"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["theonedev"]},"summary":"Regular users can escape Docker containers to gain root privileges on the host by leveraging mounted Docker sockets in CI/CD jobs.","url":"https://insights.sbomify.com/CVE-2022-39206/"}