Saturday, April 28, 2018

IBM Security Bulletin: Vulnerability in Apache POI affects IBM Maximo Asset Management (CVE-2017-12626)

Share this post:

Apache POI used by IBM Maximo Asset Management is vulnerable to a denial of service, cause by an XML External Entity Injection (XXE) error when processing XML data. By using a specially-crafted OOXML file, a remote attacker could exploit this vulnerability to consume all available CPU resources.

CVE(s): CVE-2017-12626

Affected product(s) and affected version(s):

The following Apache POI versions are affected:

  • Apache POI 3.14 and earlier releases

IBM supplied Apache POI with the following:

The 7.5.0.x and 7.6.0.x versions of Maximo Asset Management bundled Apache POI 3.7, 3.8, and 3.14.

This vulnerability affects the following versions of the IBM Maximo Asset Management core product, and all other IBM Maximo Industry Solution and IBM Control Desk products, regardless of their own version, if they are currently installed on top of an affected IBM Maximo Asset Management. *

Maximo Asset Management core product affected versions:
Maximo Asset Management 7.6, 7.5
Maximo Asset Management Essentials 7.5

Industry Solutions products affected if using an affected core version:
Maximo for Aviation
Maximo for Government
Maximo for Life Sciences
Maximo for Nuclear Power
Maximo for Oil and Gas
Maximo for Transportation
Maximo for Utilities

IBM Control Desk products affected if using an affected core version:
SmartCloud Control Desk
IBM Control Desk
Tivoli Integration Composer

* To determine the core product version, log in and view System Information. The core product version is the “Tivoli’s process automation engine” version. Please consult the Product Coexistence Matrix for a list of supported product combinations.

Refer to the following reference URLs for remediation and additional vulnerability details:
Source Bulletin: http://www-01.ibm.com/support/docview.wss?uid=swg22015901
X-Force Database: https://exchange.xforce.ibmcloud.com/vulnerabilities/138361



from IBM Product Security Incident Response Team https://ift.tt/2FoCBRF

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.