CVE-2018-5224
Bamboo Windows Command Injection Vulnerability
Description
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 create a repository in Bamboo, edit an existing plan in Bamboo that has a non-linked Mercurial repository, or create a plan in Bamboo either globally or in a project using Bamboo Specs can 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.
INFO
Published Date :
March 29, 2018, 1:29 p.m.
Last Modified :
April 24, 2018, 12:58 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
5.9
Exploitability Score :
2.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2018-5224
.
URL | Resource |
---|---|
http://www.securityfocus.com/bid/103653 | Third Party Advisory VDB Entry |
https://confluence.atlassian.com/x/PS9sO | Mitigation Vendor Advisory |
https://jira.atlassian.com/browse/BAM-19743 | Vendor Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2018-5224
vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2018-5224
vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Apr. 24, 2018
Action Type Old Value New Value Added CVSS V2 (AV:N/AC:L/Au:S/C:C/I:C/A:C) Added CVSS V3 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Changed Reference Type https://jira.atlassian.com/browse/BAM-19743 No Types Assigned https://jira.atlassian.com/browse/BAM-19743 Vendor Advisory Changed Reference Type http://www.securityfocus.com/bid/103653 No Types Assigned http://www.securityfocus.com/bid/103653 Third Party Advisory, VDB Entry Changed Reference Type https://confluence.atlassian.com/x/PS9sO No Types Assigned https://confluence.atlassian.com/x/PS9sO Mitigation, Vendor Advisory Added CWE CWE-20 Added CPE Configuration AND OR *cpe:2.3:a:atlassian:bamboo:*:*:*:*:*:*:*:* versions from (including) 2.7.0 up to (excluding) 6.3.3 *cpe:2.3:a:atlassian:bamboo:*:*:*:*:*:*:*:* versions from (including) 6.4.0 up to (excluding) 6.4.1 OR cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:* -
CVE Modified by [email protected]
Apr. 06, 2018
Action Type Old Value New Value Added Reference http://www.securityfocus.com/bid/103653 [No Types Assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2018-5224
is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2018-5224
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.37 }} -0.00%
score
0.71979
percentile