Bamboo Security Advisory 2016-07-20
Bamboo - Deserialisation resulting in remote code execution caused by insufficient restriction on permitted deserialised classes.
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.
Date of Advisory: 10 AM PDT (Pacific Time, -7 hours)
- CVE-2016-5229 - Deserialisation in Bamboo.
Affected Bamboo product versions:
- 2.3.1 <= version < 184.108.40.206
- 5.12.0 <= version < 220.127.116.11
Note: Bamboo version 5.10.0 and higher are not vulnerable if the "whitelist" option for XStream Serialisation is active. Prior to the fix versions listed below Bamboo defaulted to using a blacklist approach for XStream Serialisation. See Serialization protection methods for information on serialisation settings.
Fixed Bamboo product versions:
- for 5.11.x, Bamboo 18.104.22.168 has been released with a fix for this issue.
- for 5.12.x, Bamboo 22.214.171.124 has been released with a fix for this issue.
Summary of Vulnerability
This advisory discloses a critical severity security vulnerability which was introduced in version 2.3.1 of Bamboo. Versions of Bamboo starting with 2.3.1 before 126.96.36.199 (the fixed version for 5.11.x) and from 5.12.0 before 188.8.131.52 (the fixed version for 5.12.x) are affected by this vulnerability.
Atlassian Cloud instances have already been upgraded to a version of Bamboo which does not have the issue described on this page.
Customers who have upgraded Bamboo to version 184.108.40.206 or version 220.127.116.11 are not affected.
Customers who have downloaded and installed Bamboo >= 2.3.1 less than 18.104.22.168 (the fixed version for 5.11.x)
Customers who have downloaded and installed Bamboo >= 5.12.0 less than 22.214.171.124 (the fixed version for 5.12.x)
Please upgrade your Bamboo installations immediately to fix this vulnerability.
We would like to credit Moritz Bechler of AgNO3 for reporting this issue to us.
Deserialisation resulting in remote code execution caused by insufficient restriction on permitted deserialised classes (CVE-2016-5229)
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 an independent assessment and you should evaluate its applicability to your own IT environment.
Bamboo had a resource that deserialised input from build agents and did not sufficiently restrict which classes could be deserialised. To exploit this issue, attackers need to have a valid Bamboo agent fingerprint or be able to run code on a Bamboo agent.
All versions of Bamboo from 2.3.1 before 126.96.36.199 (the fixed version for 5.11.x) and from 5.12.0 before 188.8.131.52 (the fixed version for 5.12.x) are affected by this vulnerability. This issue can be tracked here: - BAM-17736Getting issue details... STATUS
This issue can be mitigated in Bamboo version 5.10.0 and higher by setting the XStream Serialisation setting to "whitelist" which prior to the fix versions detailed in this advisory was not the default. See Serialization protection methods for information on serialisation settings.
We have taken the follow steps to address this issue:
- Released Bamboo version 184.108.40.206 that contains fixes for this issue.
- Released Bamboo version 220.127.116.11 that contains fixes for this issue.
What You Need to Do
The vulnerabilities and fix versions are described in the description section above. Atlassian recommends that you upgrade to the latest version. This upgrade will automatically reconfigure your Bamboo to use a secure deserialisation mode.
Upgrade Bamboo to version 18.104.22.168 or higher.
If you are running Bamboo 5.11.x and cannot upgrade to bamboo 22.214.171.124 then upgrade to version 126.96.36.199.
If you are running Bamboo 5.10.x and cannot upgrade to 188.8.131.52 or 184.108.40.206 then you can follow following steps to mitigate the issue:
- Log in to Bamboo as an administrator and go to Bamboo administration > Security > Security settings which is found at
- Under the Serialization protection methods section, set the XStream setting to Whitelist.
- Check that XStream is set to Whitelist after reloading the Security Settings page.
See Serialization protection methods for information on serialisation settings.
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 to major software versions for up to 12 months for JIRA and Confluence. We will release new maintenance releases for the versions covered by the new policy instead of binary patches.
Binary patches will no longer be 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.|
|サポート終了ポリシー||Our end of life policy varies for different products. Please refer to our EOL Policy for details.|