{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-29184 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-29184 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-29184 is a high-severity command injection vulnerability in gocd, published on 20 May 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-29184 and fix it if it is affected.\n\nWhat it is: CVE-2022-29184 is a high-severity command injection vulnerability in gocd, published on 20 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-29184 in the wild and no public exploit code.\n\nAffected product: gocd. 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-29184/ (Markdown: https://insights.sbomify.com/CVE-2022-29184/index.md)","id":"CVE-2022-29184","markdown":"https://insights.sbomify.com/CVE-2022-29184/index.md","name":"CVE-2022-29184","record":{"aliases":["GHSA-vf5r-r7j2-cf2h"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"GoCD continuous delivery server","requires_auth":"low_privilege","summary":"Authenticated users with pipeline editing permissions can achieve remote code execution on the GoCD server by exploiting Mercurial hooks via malicious branch names.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gocd","vendor":"thoughtworks"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"},{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"GoCD is a continuous delivery server. In GoCD versions prior to 22.1.0, it is possible for existing authenticated users who have permissions to edit or create pipeline materials or pipeline configuration repositories to get remote code execution capability on the GoCD server via configuring a malicious branch name which abuses Mercurial hooks/aliases to exploit a command injection weakness. An attacker would require access to an account with existing GoCD administration permissions to either create/edit (`hg`-based) configuration repositories; create/edit pipelines and their (`hg`-based) materials; or, where \"pipelines-as-code\" configuration repositories are used, to commit malicious configuration to such an external repository which will be automatically parsed into a pipeline configuration and (`hg`) material definition by the GoCD server. This issue is fixed in GoCD 22.1.0. As a workaround, users who do not use/rely upon Mercurial materials can uninstall/remove the `hg`/Mercurial binary from the underlying GoCD Server operating system or Docker image.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Command Injection/Argument Injection in GoCD","id":"CVE-2022-29184","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Observable Timing Discrepancy in totp-rs","id":"CVE-2022-29185"},"packages":[],"prev":{"headline":"Reflected XSS in GoCD","id":"CVE-2022-29183"},"products":["gocd"],"published":"2022-05-20","related":[{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2021-43290","kev_date_added":null,"published":"2022-04-14"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2021-44659","kev_date_added":null,"published":"2021-12-22"},{"cvss_score":9.4,"headline":"GoCD vulnerable to admin privilege escalation by a malicious internal/existing authenticated user","id":"CVE-2024-56320","kev_date_added":null,"published":"2025-01-03"},{"cvss_score":9.1,"headline":"Compromised agents may be able to execute remote code on GoCD Server","id":"CVE-2022-39311","kev_date_added":null,"published":"2022-10-14"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2021-43286","kev_date_added":null,"published":"2022-04-14"},{"cvss_score":8.8,"headline":"Cross-site request forgery in gocd","id":"CVE-2021-25924","kev_date_added":null,"published":"2021-04-01"}],"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-04-23","vendors":["gocd"]},"summary":"Authenticated users with pipeline editing permissions can achieve remote code execution on the GoCD server by exploiting Mercurial hooks via malicious branch names.","url":"https://insights.sbomify.com/CVE-2022-29184/"}