Security Bulletin: An XML External Entity (XXE) processing vulnerability is exposed in Case Manager administration client (CVE-2018-1844)

Summary

IBM Case Manager has addressed the following vulnerability. An XML External Entity (XXE) processing vulnerability is exposed in Case Manager administration client with the ability to import solution packaged which are FileNet Deployment Manager exported zip packages. (CVE-2018-1844)

Vulnerability Details

CVEID: CVE-2018-1844 DESCRIPTION: IBM Case Manager is vulnerable to a XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources.
CVSS Base Score: 7.1
CVSS Temporal Score: See <https://exchange.xforce.ibmcloud.com/vulnerabilities/150904&gt; for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L)

Affected Products and Versions

Remediation/Fixes

Product

|

VRMF

|

APAR

|

Remediation/First Fix

—|—|—|—
IBM Case Manager | 5.3.0.0 - 5.3.3.0 | PJ45232 | 5.3.3.0-ICM-IF003 or later versions
IBM Case Manager | 5.2.1.0 - 5.2.1.7 | PJ45226 | 5.2.1.7-ICM-IF004 or later

The fix will require the application server running IBM Case Manager to be configured with Java 8. Please refer to application server documentation on the application server requirements and configuration changes needed to run with Java 8.

IBM Case Manager V5.2.0 is not fixed as the fix requires JDK 1.8 and this will not be compatible with the application server versions that is supported with this version of Case Manager. IBM recommends upgrading to a fixed, supported version/release/platform of the product.

IBM Case Manager V5.1.1 is no longer in full support; IBM recommends upgrading to a fixed, supported version/release/platform of the product.

Workarounds and Mitigations

The issue can be mitigated by preventing XXE injection into the solution zip package in doing the following:

1. Ensuring that the solution package export and import process is well controlled, where the package is not exposed to modification.
2. Generating a checksum for the solution export zip package immediately after export, and validating the checksum prior to import to ensure package consistency.