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.
References
Link | Resource |
---|---|
https://github.com/gocd/gocd/commit/37d35115db2ada2190173f9413cfe1bc6c295ecb | Patch Third Party Advisory |
https://github.com/gocd/gocd/releases/tag/22.1.0 | Release Notes Third Party Advisory |
https://github.com/gocd/gocd/security/advisories/GHSA-vf5r-r7j2-cf2h | Third Party Advisory |
https://www.gocd.org/releases/#22-1-0 | Release Notes Vendor Advisory |
Configurations
History
No history.
Information
Published : 2022-05-20 20:15
Updated : 2024-02-28 19:09
NVD link : CVE-2022-29184
Mitre link : CVE-2022-29184
CVE.ORG link : CVE-2022-29184
JSON object : View
Products Affected
thoughtworks
- gocd