Bamboo Security Advisory 2018-03-28
Bamboo - Argument injection through Mercurial repository URI handling on Windows - CVE-2018-5224
Note: As of September 2014 we are no longer issuing binary bug patches, instead we create new maintenance releases for the major versions we are backporting.
CVE-2018-5224 - Argument injection through Mercurial repository URI handling on Windows
|Advisory Release Date|
10 AM PDT (Pacific Time, -7 hours)
Affected Bamboo Versions
Fixed Bamboo Versions
Summary of Vulnerability
This advisory discloses a critical severity security vulnerability which was introduced in version 2.7.0 of Bamboo. Versions of Bamboo starting with 2.7.0 before 6.3.3 (the fixed version for 6.3.x) and from version 6.4.0 before 6.4.1 (the fixed version for 6.4.x) running on the Windows operating system are affected by this vulnerability.
Customers who have upgraded Bamboo to version 6.3.3 or 6.4.1 are not affected.
Customers who do not run Bamboo on the Windows operating system are not affected.
Customers using Bamboo Server on Windows, who have downloaded and installed Bamboo >= 2.7.0 less than 6.3.3 (the fixed version for 6.3.x)
Customers using Bamboo Server on Windows, who have downloaded and installed Bamboo >= 6.4.0 less than 6.4.1 (the fixed version for 6.4.x)
Please upgrade your Bamboo installations immediately to fix this vulnerability.
Argument injection through Mercurial repository URI handling on Windows (CVE-2018-5224)
Atlassian rates the severity level of this vulnerability as critical, according to the scale published in our Atlassian severity levels. The scale allows us to rank the severity as critical, high, moderate or low.
This is our assessment and you should evaluate its applicability to your own IT environment.
Bamboo did not correctly check if a configured Mercurial repository URI contained values that the Windows operating system may consider argument parameters. An attacker who has permission to do one or more of the following:
- create a repository in Bamboo
- edit an existing plan in Bamboo that has a non-linked Mercurial repository
- create a plan in Bamboo either globally or in a project using Bamboo Specs
can execute code of their choice on systems that run a vulnerable version of Bamboo on the Windows operating system.
All versions of Bamboo starting with 2.7.0 before 6.3.3 (the fixed version for 6.3.x) and from version 6.4.0 before 6.4.1 (the fixed version for 6.4.x) running on the Windows operating system are affected by this vulnerability.
This issue can be tracked here: https://jira.atlassian.com/browse/BAM-19743.
Atlassian would like to credit Zhang Tianqi @ Tophant for reporting this issue to us.
Disable the "Atlassian Bamboo Mercurial Repository Plugin" via the Addons menu in the Administration section.
Note: "Atlassian Bamboo Bitbucket Repository Plugin" depends on "Atlassian Bamboo Mercurial Repository Plugin" therefore it will be disabled as well, as an effect any Bitbucket Cloud repository in Bamboo will stop working. Reenabling "Atlassian Bamboo Bitbucket Repository Plugin" will reenable "Atlassian Bamboo Mercurial Repository Plugin" making your system vulnerable again.
We have taken the following steps to address this issue:
- Released Bamboo version 6.4.1 that contains a fix for this issue and can be downloaded from https://www.atlassian.com/software/bamboo/download.
- Released Bamboo version 6.3.3 that contains a fix for this issue and can be downloaded from https://www.atlassian.com/software/bamboo/download-archives.
What You Need to Do
Atlassian recommends that you upgrade to the latest version. For a full description of the latest version of Bamboo, see the release notes. You can download the latest version of Bamboo from the download centre.
Upgrade Bamboo to version 6.4.1 or higher.
If you are running Bamboo 6.3.x and cannot upgrade to 6.4.1 then upgrade to version 6.3.3.
If you did not receive an email for this advisory and you wish to receive such emails in the future go to https://my.atlassian.com/email and subscribe to Alerts emails.
If you have questions or concerns regarding this advisory, please raise a support request at https://support.atlassian.com/.
|Security Bug fix Policy|
As per our new policy critical security bug fixes will be back ported in accordance with https://www.atlassian.com/trust/security/bug-fix-policy. We will release new maintenance releases for the versions covered by the new policy instead of binary patches.
Binary patches are no longer released.
|Severity Levels for security issues||Atlassian security advisories include a severity level and a CVE identifier. This severity level is based on our self-calculated CVSS score for each specific vulnerability. CVSS is an industry standard vulnerability metric. You can also learn more about CVSS at FIRST.org.|
|End of Life Policy||Our end of life policy varies for different products. Please refer to our EOL Policy for details.|
Was this helpful?Yes Provide feedback about this article