Bamboo did not check that the name of a branch in a Mercurial repository contained argument parameters. An attacker who has permission to create a repository in Bamboo, edit an existing plan that has a non-linked Mercurialrepository, create or edit a plan when there is at least one linked Mercurial repository that the attacker has permission to use, or commit to a Mercurial repository used by a Bamboo plan which has branch detection enabled can execute code of their choice on systems that run a vulnerable version of Bamboo Server. Versions of Bamboo starting with 2.7.0 before 6.1.6 (the fixed version for 6.1.x) and from 6.2.0 before 6.2.5 (the fixed version for 6.2.x) are affected by this vulnerability.
References
Link | Resource |
---|---|
http://www.securityfocus.com/bid/102193 | Third Party Advisory VDB Entry |
https://confluence.atlassian.com/bamboo/bamboo-security-advisory-2017-12-13-939939816.html | Patch Vendor Advisory |
https://jira.atlassian.com/browse/BAM-18843 | Issue Tracking Patch Vendor Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: atlassian
Published: 2017-12-12T00:00:00
Updated: 2017-12-15T10:57:01
Reserved: 2017-09-19T00:00:00
Link: CVE-2017-14590
JSON object: View
NVD Information
Status : Analyzed
Published: 2017-12-13T15:29:00.297
Modified: 2019-10-03T00:03:26.223
Link: CVE-2017-14590
JSON object: View
Redhat Information
No data.
CWE