CVE-2017-14590: Critical severity bamboo vulnerability
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.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is CVE-2017-14590?
CVE-2017-14590 is a vulnerability in Bamboo, an Atlassian product, that allows an attacker with repository creation/editing permissions to execute malicious code.
How severe is CVE-2017-14590?
CVE-2017-14590 has a severity level of 9.1 (critical).
Which software versions are affected by CVE-2017-14590?
Bamboo versions 2.7.0 to 6.1.6, as well as versions 6.2.0 to 6.2.5, are affected by CVE-2017-14590.
How can I fix CVE-2017-14590?
To fix CVE-2017-14590, it is recommended to upgrade Bamboo to version 6.2.6 or higher.
Where can I find more information about CVE-2017-14590?
You can find more information about CVE-2017-14590 in the references provided: Security Focus, Atlassian's Bamboo Security Advisory, and Atlassian's JIRA.