Bamboo Security Advisory 2016-01-20

Bamboo - Deserialisation resulting in remote code execution and missing authentication exposed services.

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 PST(Pacific Standard Time, -8 hours)

CVE IDs: 

  • CVE-2014-9757 - Deserialisation in Smack.
  • CVE-2015-8360 - Deserialisation in Bamboo.
  • CVE-2015-8361 - Missing authentication checks in exposed services.

 

Product: Bamboo

Affected Bamboo product versions: 

  • 2.3.1 <= version < 5.9.9

Fixed Bamboo product versions:

  • for 5.9.x, Bamboo 5.9.9 has been released with a fix for this issue.
  • for 5.10.x, Bamboo 5.10.0 has been released with a fix for this issue.

Summary of Vulnerability

This advisory discloses multiple critical severity security vulnerabilities of which the earliest vulnerability was introduced in version 2.3.1 of BambooVersions of Bamboo starting with 2.3.1 before 5.9.9 (the fixed version for 5.9.x) are vulnerable. 

 

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 5.9.9 or version 5.10.0 are not affected

Customers who have downloaded and installed Bamboo >= 2.3.1 less than 5.9.9 (the fixed version for 5.9.x)

Please upgrade your Bamboo installations immediately to fix this vulnerability.

Deserialisation Through Smack Resulting in Remote Code Execution Vulnerability (CVE-2014-9757)

Severity

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 a severity as critical, high, moderate, or low.

This is an independent assessment and you should evaluate its applicability to your own IT environment.

Description

Bamboo used an old version of the Smack XMPP library that deserialises messages received from XMPP. Attackers can use this vulnerability to execute Java code of their choice on systems that have a vulnerable version of Bamboo if a XMPP connection has been configured. To exploit this issue, Bamboo attackers need to be able to modify XMPP messages destined to Bamboo from a configured XMPP server.

All versions of Bamboo from 2.4 before 5.9.9 (the fixed version for 5.9.x) are affected by this vulnerability. This issue can be tracked here:  BAM-17099 - Getting issue details... STATUS


Deserialisation Resulting in Remote Code Execution Vulnerability (CVE-2015-8360)

Severity

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 a severity as critical, high, moderate, or low.

This is an independent assessment and you should evaluate its applicability to your own IT environment.

Description

Bamboo had a resource that deserialised arbitrary user input without restriction. Attackers can use this vulnerability to execute Java code of their choice on systems that have a vulnerable version of Bamboo. To exploit this issue, attackers need to be able to access the Bamboo JMS port (port 54663 by default).

All versions of Bamboo from 2.3.1 before 5.9.9 (the fixed version for 5.9.x) are affected by this vulnerability. This issue can be tracked here:  BAM-17101 - Getting issue details... STATUS

 

Services exposed without authentication Vulnerability (CVE-2015-8361)

Severity

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 a severity as critical, high, moderate, or low.

This is an independent assessment and you should evaluate its applicability to your own IT environment.

Description

Bamboo exposed services without first performing authentication checks. Attackers can use this vulnerability to extract confidential information from Bamboo, modify certain settings and manage build agents. To exploit this issue, attackers need to be able to access the Bamboo JMS port.

All versions of Bamboo from 2.4 before 5.9.9 (the fixed version for 5.9.x) are affected by this vulnerability. This issue can be tracked here:  BAM-17102 - Getting issue details... STATUS

 

Fix

We have taken the follow steps to address these issues:

  1. Released Bamboo version 5.10.0 that contains fixes for these issues.
  2. Released Bamboo version 5.9.9 that contains fixes for this issues.

What You Need to Do

Upgrade (recommended)

The vulnerabilities and fix versions are described in the Description section above. Atlassian recommends that you upgrade to the latest version. 

 

Upgrade Bamboo to version 5.9.9 or higher.

If you are running Bamboo 5.9.x and cannot upgrade to bamboo 5.10.xthen upgrade to version 5.9.9.

(warning) A bug has been identified in Bamboo 5.9.9 which prevents builds using git repositories via SSH from working. See the associated bug record for workarounds:  BAM-17131 - Getting issue details... STATUS . This bug was fixed in Bamboo 5.9.10, available from the download archive. Bamboo 5.10 is not affected by this bug.


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.

Support

If you have questions or concerns regarding this advisory, please raise a support request at https://support.atlassian.com/.

References

Security Bug fix Policy

As per our new policy critical security bug fixes will be backported for the previous major release version. 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 issuesAtlassian 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 PolicyOur end of life policy varies for different products. Please refer to our EoL Policy for details. 



Last modified on Aug 23, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.