Page History
Warning |
---|
This is a public space: For the draft, please restrict the page during creation and |
English | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Dear customer, Atlassian has published on Wednesday a critical security advisory pointing to a security vulnerability in "Insight - Asset Management App" respectively "Jira Service Management Data Center". Affected versions Insight - Asset Management version:
Jira Service Management Data Center version:
Fixed versions - Insight - Asset Management Marketplace App 8.9.3 Fixed versions - Jira Service Management Data Center 4.20.0 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 (known as Jira Service Desk prior to 4.14) from version 4.15.0 onwards. All versions of Jira Service Management Data Center >= 4.15.0 and < 4.20 are impacted. Affected versions of the Insight - Asset Management app and Jira Service Management Data Center are listed in the table above (see Affected Versions)
CVE-2018-10054 - RCE in Insight - Asset Management impacting Jira Service Management Data Center
|
Info |
---|
Jira Service Management Data Center versions 4.15.0 and greater have Insight - Asset Management already bundled. |
Info |
---|
Jira Core (Server/DC), Jira Software (Server/DC), and Jira Service Management (Server) instances that use H2 DB without Insight - Asset Management installed from the Marketplace aren't affected by this vulnerability. |
This issue can be tracked here (currently restricted to Atlassian staff): - JSDSERVER-8716Jira Service Management / Insight Asset Management vulnerable to RCE Security
Fix
We have taken the following steps to address this issue:
Released versions 4.20.0 of Jira Service Management Data Center 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.
Upgrade
Jira Service Management Data Center
For Jira Service Management Data Center version 4.15.0 and greater, upgrade to 4.20.0 by downloading this version from our software downloads page.
Insight - Asset Management app
For:
Jira Service Management Data Center 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.
Warning |
---|
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 | Administering Jira applications Data Center and Server 8.19 | Atlassian Documentation. |
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.jar
file and delete it (where “XYZ” is a placeholder for the version of the file, e.g.h2-1.4.200.jar
)Start Jira again
Info |
---|
In a Data Center environment, a rolling restart of the nodes is sufficient after deleting the JAR. |