ID CVE-2015-6576
Summary Bamboo 2.2 before 5.8.5 and 5.9.x before 5.9.7 allows remote attackers with access to the Bamboo web interface to execute arbitrary Java code via an unspecified resource.
References
Vulnerable Configurations
  • Atlassian Bamboo 2.2
    cpe:2.3:a:atlassian:bamboo:2.2
  • Atlassian Bamboo 2.2.1
    cpe:2.3:a:atlassian:bamboo:2.2.1
  • Atlassian Bamboo 2.2.2
    cpe:2.3:a:atlassian:bamboo:2.2.2
  • Atlassian Bamboo 2.2.3
    cpe:2.3:a:atlassian:bamboo:2.2.3
  • Atlassian Bamboo 2.2.4
    cpe:2.3:a:atlassian:bamboo:2.2.4
  • Atlassian Bamboo 2.3
    cpe:2.3:a:atlassian:bamboo:2.3
  • Atlassian Bamboo 2.3.1
    cpe:2.3:a:atlassian:bamboo:2.3.1
  • Atlassian Bamboo 2.4
    cpe:2.3:a:atlassian:bamboo:2.4
  • Atlassian Bamboo 2.4.1
    cpe:2.3:a:atlassian:bamboo:2.4.1
  • Atlassian Bamboo 2.4.2
    cpe:2.3:a:atlassian:bamboo:2.4.2
  • Atlassian Bamboo 2.4.3
    cpe:2.3:a:atlassian:bamboo:2.4.3
  • Atlassian Bamboo 2.5
    cpe:2.3:a:atlassian:bamboo:2.5
  • Atlassian Bamboo 2.5.1
    cpe:2.3:a:atlassian:bamboo:2.5.1
  • Atlassian Bamboo 2.5.2
    cpe:2.3:a:atlassian:bamboo:2.5.2
  • Atlassian Bamboo 2.5.3
    cpe:2.3:a:atlassian:bamboo:2.5.3
  • Atlassian Bamboo 2.5.5
    cpe:2.3:a:atlassian:bamboo:2.5.5
  • Atlassian Bamboo 2.6
    cpe:2.3:a:atlassian:bamboo:2.6
  • Atlassian Bamboo 2.6.1
    cpe:2.3:a:atlassian:bamboo:2.6.1
  • Atlassian Bamboo 2.6.2
    cpe:2.3:a:atlassian:bamboo:2.6.2
  • Atlassian Bamboo 2.6.3
    cpe:2.3:a:atlassian:bamboo:2.6.3
  • Atlassian Bamboo 2.7
    cpe:2.3:a:atlassian:bamboo:2.7
  • Atlassian Bamboo 2.7.1
    cpe:2.3:a:atlassian:bamboo:2.7.1
  • Atlassian Bamboo 2.7.2
    cpe:2.3:a:atlassian:bamboo:2.7.2
  • Atlassian Bamboo 2.7.3
    cpe:2.3:a:atlassian:bamboo:2.7.3
  • Atlassian Bamboo 2.7.4
    cpe:2.3:a:atlassian:bamboo:2.7.4
  • Atlassian Bamboo 3.0
    cpe:2.3:a:atlassian:bamboo:3.0
  • Atlassian Bamboo 3.0.1
    cpe:2.3:a:atlassian:bamboo:3.0.1
  • Atlassian Bamboo 3.0.2
    cpe:2.3:a:atlassian:bamboo:3.0.2
  • Atlassian Bamboo 3.0.3
    cpe:2.3:a:atlassian:bamboo:3.0.3
  • Atlassian Bamboo 3.1
    cpe:2.3:a:atlassian:bamboo:3.1
  • Atlassian Bamboo 3.1.1
    cpe:2.3:a:atlassian:bamboo:3.1.1
  • Atlassian Bamboo 3.1.3
    cpe:2.3:a:atlassian:bamboo:3.1.3
  • Atlassian Bamboo 3.1.4
    cpe:2.3:a:atlassian:bamboo:3.1.4
  • Atlassian Bamboo 3.2
    cpe:2.3:a:atlassian:bamboo:3.2
  • Atlassian Bamboo 3.2.2
    cpe:2.3:a:atlassian:bamboo:3.2.2
  • Atlassian Bamboo 3.3
    cpe:2.3:a:atlassian:bamboo:3.3
  • Atlassian Bamboo 3.3.1
    cpe:2.3:a:atlassian:bamboo:3.3.1
  • Atlassian Bamboo 3.3.2
    cpe:2.3:a:atlassian:bamboo:3.3.2
  • Atlassian Bamboo 3.3.3
    cpe:2.3:a:atlassian:bamboo:3.3.3
  • Atlassian Bamboo 3.3.4
    cpe:2.3:a:atlassian:bamboo:3.3.4
  • Atlassian Bamboo 3.4
    cpe:2.3:a:atlassian:bamboo:3.4
  • Atlassian Bamboo 3.4.1
    cpe:2.3:a:atlassian:bamboo:3.4.1
  • Atlassian Bamboo 3.4.2
    cpe:2.3:a:atlassian:bamboo:3.4.2
  • Atlassian Bamboo 3.4.3
    cpe:2.3:a:atlassian:bamboo:3.4.3
  • Atlassian Bamboo 3.4.4
    cpe:2.3:a:atlassian:bamboo:3.4.4
  • Atlassian Bamboo 3.4.5
    cpe:2.3:a:atlassian:bamboo:3.4.5
  • Atlassian Bamboo 4.0
    cpe:2.3:a:atlassian:bamboo:4.0
  • Atlassian Bamboo 4.0.1
    cpe:2.3:a:atlassian:bamboo:4.0.1
  • Atlassian Bamboo 4.1
    cpe:2.3:a:atlassian:bamboo:4.1
  • Atlassian Bamboo 4.1.1
    cpe:2.3:a:atlassian:bamboo:4.1.1
  • Atlassian Bamboo 4.1.2
    cpe:2.3:a:atlassian:bamboo:4.1.2
  • Atlassian Bamboo 4.2
    cpe:2.3:a:atlassian:bamboo:4.2
  • Atlassian Bamboo 4.2.1
    cpe:2.3:a:atlassian:bamboo:4.2.1
  • Atlassian Bamboo 4.3
    cpe:2.3:a:atlassian:bamboo:4.3
  • Atlassian Bamboo 4.3.1
    cpe:2.3:a:atlassian:bamboo:4.3.1
  • Atlassian Bamboo 4.3.2
    cpe:2.3:a:atlassian:bamboo:4.3.2
  • Atlassian Bamboo 4.3.3
    cpe:2.3:a:atlassian:bamboo:4.3.3
  • Atlassian Bamboo 4.3.4
    cpe:2.3:a:atlassian:bamboo:4.3.4
  • Atlassian Bamboo 4.4
    cpe:2.3:a:atlassian:bamboo:4.4
  • Atlassian Bamboo 4.4.1
    cpe:2.3:a:atlassian:bamboo:4.4.1
  • Atlassian Bamboo 4.4.2
    cpe:2.3:a:atlassian:bamboo:4.4.2
  • Atlassian Bamboo 4.4.3
    cpe:2.3:a:atlassian:bamboo:4.4.3
  • Atlassian Bamboo 4.4.4
    cpe:2.3:a:atlassian:bamboo:4.4.4
  • Atlassian Bamboo 4.4.5
    cpe:2.3:a:atlassian:bamboo:4.4.5
  • Atlassian Bamboo 4.4.8
    cpe:2.3:a:atlassian:bamboo:4.4.8
  • Atlassian Bamboo 5.0
    cpe:2.3:a:atlassian:bamboo:5.0
  • Atlassian Bamboo 5.0 Beta1
    cpe:2.3:a:atlassian:bamboo:5.0:beta1
  • Atlassian Bamboo 5.0 Beta2
    cpe:2.3:a:atlassian:bamboo:5.0:beta2
  • Atlassian Bamboo 5.0 Beta3
    cpe:2.3:a:atlassian:bamboo:5.0:beta3
  • Atlassian Bamboo 5.0 Release Candidate 1
    cpe:2.3:a:atlassian:bamboo:5.0:rc1
  • Atlassian Bamboo 5.0.1
    cpe:2.3:a:atlassian:bamboo:5.0.1
  • Atlassian Bamboo 5.1
    cpe:2.3:a:atlassian:bamboo:5.1
  • Atlassian Bamboo 5.1.1
    cpe:2.3:a:atlassian:bamboo:5.1.1
  • Atlassian Bamboo 5.2
    cpe:2.3:a:atlassian:bamboo:5.2
  • Atlassian Bamboo 5.2.1
    cpe:2.3:a:atlassian:bamboo:5.2.1
  • Atlassian Bamboo 5.2.2
    cpe:2.3:a:atlassian:bamboo:5.2.2
  • Atlassian Bamboo 5.3
    cpe:2.3:a:atlassian:bamboo:5.3
  • Atlassian Bamboo 5.4
    cpe:2.3:a:atlassian:bamboo:5.4
  • Atlassian Bamboo 5.4.1
    cpe:2.3:a:atlassian:bamboo:5.4.1
  • Atlassian Bamboo 5.4.2
    cpe:2.3:a:atlassian:bamboo:5.4.2
  • Atlassian Bamboo 5.5
    cpe:2.3:a:atlassian:bamboo:5.5
  • Atlassian Bamboo 5.6
    cpe:2.3:a:atlassian:bamboo:5.6
  • Atlassian Bamboo 5.6.1
    cpe:2.3:a:atlassian:bamboo:5.6.1
  • Atlassian Bamboo 5.6.2
    cpe:2.3:a:atlassian:bamboo:5.6.2
  • Atlassian Bamboo 5.7
    cpe:2.3:a:atlassian:bamboo:5.7
  • Atlassian Bamboo 5.7.1
    cpe:2.3:a:atlassian:bamboo:5.7.1
  • Atlassian Bamboo 5.7.2
    cpe:2.3:a:atlassian:bamboo:5.7.2
  • Atlassian Bamboo 5.8
    cpe:2.3:a:atlassian:bamboo:5.8
  • Atlassian Bamboo 5.8.1
    cpe:2.3:a:atlassian:bamboo:5.8.1
  • Atlassian Bamboo 5.8.2
    cpe:2.3:a:atlassian:bamboo:5.8.2
CVSS
Base: 6.5
Impact:
Exploitability:
CWE CWE-94
CAPEC
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Manipulating User-Controlled Variables
    This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An attacker can override environment variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the attacker can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.
nessus via4
NASL family CGI abuses
NASL id BAMBOO_5_8_5.NASL
description According to its self-reported version number, the instance of Atlassian Bamboo running on the remote host is version 2.2.x prior to 5.8.5 or 5.9.x prior to 5.9.7. It is, therefore, affected by an unspecified resource deserialization flaw due to improper validation of user-supplied input. An unauthenticated, remote attacker can exploit this to execute arbitrary Java code. Note that the attacker must be able to access the Bamboo web interface. Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.
last seen 2019-02-21
modified 2018-06-13
plugin id 86721
published 2015-11-04
reporter Tenable
source https://www.tenable.com/plugins/index.php?view=single&id=86721
title Atlassian Bamboo 2.2.x < 5.8.5 / 5.9.x < 5.9.7 Unspecified Resource Deserialization RCE
refmap via4
bugtraq 20151023 CVE-2015-6576: Bamboo - Deserialisation resulting in remote code execution
confirm
misc http://packetstormsecurity.com/files/134065/Bamboo-Java-Code-Execution.html
Last major update 02-10-2017 - 21:29
Published 02-10-2017 - 21:29
Last modified 03-05-2019 - 13:33
Back to Top