CVE-2017-14590
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…
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (2.40%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 3.0
- 9.1 CRITICALCVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
- EPSS
- 2.40% probability · 83th percentile
- CISA KEV
- Not listed
- Affected
- atlassian/bamboo
- Source
- security@atlassian.com
References
- http://www.securityfocus.com/bid/102193Third Party Advisory, VDB Entry
- https://confluence.atlassian.com/bamboo/bamboo-security-advisory-2017-12-13-939939816.htmlPatch, Vendor Advisory
- https://jira.atlassian.com/browse/BAM-18843Issue Tracking, Patch, Vendor Advisory
- http://www.securityfocus.com/bid/102193Third Party Advisory, VDB Entry
- https://confluence.atlassian.com/bamboo/bamboo-security-advisory-2017-12-13-939939816.htmlPatch, Vendor Advisory
- https://jira.atlassian.com/browse/BAM-18843Issue Tracking, Patch, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.