Jira Service Management Security Advisory 2021-10-20
Summary | CVE-2018-10054 - Remote Code Execution through Insight - Asset Management |
|---|---|
Advisory release date | 20th Oct 2021 10 AM PDT (Pacific Time, -7 hours) (This advisory was updated on the 21st of October 2021 to clarify the affected versions of Jira Service Management Server) |
Product |
Jira Service Management Cloud customers aren't affected. |
Affected versions | Insight - Asset Management app - Marketplace download version:
Jira Service Management Data Center and Server version:
|
Fixed versions - Insight - Asset Management Marketplace App | 8.9.3 |
Fixed versions - Jira Service Management Data Center and Server | 4.20.0 (Insight v. 9.1.2 bundled) |
CVE ID(s) |
Summary of vulnerability
This advisory discloses a critical severity security vulnerability in versions of the Insight - Asset Management app prior to 8.9.3. This app is bundled with Jira Service Management Data Center and Server (known as Jira Service Desk prior to 4.14) from version 4.15.0 onwards. All versions of Jira Service Management Data Center and Server >= 4.15.0 and < 4.20 are impacted. Affected versions of the Insight - Asset Management app and Jira Service Management Data Center and Server are listed in the table above (see Affected Versions).
If you've downloaded and installed any versions listed in the Affected versions section, you must upgrade your installations to fix this vulnerability. If you are unable to upgrade immediately, apply the workaround detailed below while you plan your upgrade.
CVE-2018-10054 - RCE in Insight - Asset Management impacting Jira Service Management Data Center and Server
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 the severity as critical, high, moderate, or low.
This is our assessment and you should evaluate its applicability to your own IT environment.
Description
Insight - Asset Management has a feature to import data from several databases (DBs). One of these DBs, the H2 DB, has a native function in its library which an attacker can use to run code on the server (remote code execution a.k.a. RCE). The H2 DB is bundled with Jira to help speed up the setup of Jira test environments.
The combination of the DB import feature introduced by Insight - Asset Management with the existing Jira H2 DB library exposed this vulnerability. The vulnerability exists whether or not the import configuration was saved and even if H2 was never used as a targeted DB. Accessing this vulnerability requires the following:
- The user must be an authenticated Jira user AND
Either of the following privileges within Insight - Asset Management:
- user or group permission to “Insight administrator”
- user or group permission to “Object Schema Manager”
This issue can be tracked here: JSDSERVER-8716 - Getting issue details... STATUS
Acknowledgments
The issue was discovered by Khoadha (l0gg) of Viettel Cyber Security via the Atlassian public bug bounty program.
Fix
We have taken the following steps to address this issue:
Released versions 4.20.0 of Jira Service Management Data Center and Server and 8.9.3 of the Insight - Asset Management app, which disables the import feature from making a connection to any H2 DB.
What you need to do
Atlassian recommends that you upgrade to the latest fix version but if you can’t, you should follow the mitigation steps. For a full description of the latest version of Jira Service Management and Insight - Asset Management, see the Jira Service Management release notes.
DO NOT "Disable" or "Uninstall" Insight - Asset Management on Jira Service Management 4.19+
The bundled version of the Insight - Asset Management app in Jira Service Management Server versions 4.19 onwards appears under the "User Installed" section of "Manage Apps" but it is actually an integral part of the application. Using either the "Disable" or "Uninstall" options will break core functionality of Jira Service Management. The Data Center version correctly displays this app under "Application components". We're tracking this issue here: JSDSERVER-10845
Upgrade
Jira Service Management Data Center and Server
For Jira Service Management Data Center and Server versions 4.15.0 and greater, upgrade to 4.20.0 by downloading it from our software downloads page. Note that for these versions, you can't only upgrade the Insight app from the Marketplace as it's bundled with Jira Service Management Data Center.
Insight - Asset Management app
For:
Jira Service Management Data Center and Server versions prior to version 4.15.0,
Jira Core (Server/Data Center),
Jira Software (Server/Data Center),
upgrade the Insight - Asset Management app to version 8.9.3 (which disables the connection to any H2 DB) by downloading it from the Atlassian Marketplace.
Consider compatibility with Jira as well. The fix version (8.9.3) of the app is compatible with:
App version | Application compatibility |
|---|---|
8.9.3 | Server:
Data Center:
|
If you're running any other version, you must first upgrade to a version that is compatible with the 8.9.3 app (read our security bug fix policy for details). For example, if you're running Jira version 8.7.2 with the Insight - Asset Management app version 8.4.1, you must first upgrade to Jira version 8.12.0 or greater to be able to install the Insight - Asset Management app version 8.9.3. If you can’t upgrade immediately, follow the mitigation steps below.
Mitigation
If you’re unable to upgrade to the latest version immediately, then as a temporary workaround, you can mitigate the issue by deleting the H2 JAR file that comes with Jira installation.
The mitigation steps below will prevent any instances currently using H2 from starting up. You must migrate from the H2 database to any of the other supported database types prior to implementing the mitigation steps in order to keep using the instance.
H2 databases have never been supported in production environments.
For guidance on how to migrate databases, see Switching databases.
To remove the H2 JAR file:
Shut down Jira
Go to
<Jira-Installation-Directory>/atlassian-jira/WEB-INF/lib/Locate the
h2-1.4.XYZ.jarfile and delete it (where “XYZ” is a placeholder for the version of the file, e.g.h2-1.4.200.jar)Start Jira again
Support
If you didn't 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, raise a support request at https://support.atlassian.com/.
References
As per our new policy, critical security bug fixes will be backported in accordance with https://www.atlassian.com/trust/security/bug-fix-policy. We'll release new maintenance releases for the versions covered by the policy instead of binary patches. Binary patches are no longer released. | |
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 learn more about CVSS at FIRST.org. | |
Our End of Life policy varies for different products. Please refer to the policy for details. |