Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2017.2886
Open Source Apache POI Vulnerability for IBM DataQuant
14 November 2017
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: IBM DataQuant
Publisher: IBM
Operating System: AIX
z/OS
Windows
Linux variants
Impact/Access: Denial of Service -- Remote with User Interaction
Resolution: Mitigation
CVE Names: CVE-2017-5644
Reference: ESB-2017.2669
Original Bulletin:
http://www.ibm.com/support/docview.wss?uid=swg22010565
- --------------------------BEGIN INCLUDED TEXT--------------------
Security Bulletin: PSIRT 94056 - Open Source Apache POI Vulnerability for
IBM DataQuant
Document information
Software version: 1.1.0, 1.2.0, 2.1.0
Operating system(s): AIX, Linux, Windows, z/OS
Reference #: 2010565
Modified date: 13 November 2017
Security Bulletin
Summary
Apache POI 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.
Vulnerability Details
Apache POI 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.
Affected Products and Versions
IBM DataQuant for Multiplatforms 1.1, 1.2, and 2.1
IBM DataQuant for z/OS 1.1 and 2.1
Workarounds and Mitigations
Use the following instructions to replace DataQuant’s Apache POI library with
the latest version, which is 3.16:
1. Install 7-Zip or other file archiver.
2. Download POI 3.16 (https://archive.apache.org/dist/poi/release/bin/
poi-bin-3.16-20170419.zip). Find the following jar files inside the archive:
poi-3.16.jar
poi-ooxml-3.16.jar
poi-ooxml-schemas-3.16.jar
commons-collections4-4.1.jar (under "lib" folder)
commons-codec-1.10.jar (under "lib" folder)
commons-logging-1.2.jar (under "lib" folder)
curvesapi-1.04.jar (under "ooxml-lib" folder)
xmlbeans-2.6.0.jar (under "ooxml-lib" folder)
3. In the DataQuant for Workstation\plugins folder, rename
com.ibm.bi.core.poi_2.1.7.20170216.jar to
com.ibm.bi.core.poi_2.1.7.20170216.zip and open it in the archiver that you
have installed in step 1.
- - Remove everything from the "lib" folder.
- - Copy the
poi-3.16.jar,poi-ooxml-3.16.jar,poi-ooxml-schemas-3.16.jar,xmlbeans-2.6.0.jar,curvesapi-1.04.jar,commons-collections4-4.1.jar
files into the "lib" folder.
- - Modify the META-INF\MANIFEST-MF file. Instead of:
Bundle-ClassPath: .,lib/poi-3.12-20150511.jar,lib/poi-ooxml-3.12-20150
511.jar,lib/poi-ooxml-schemas-3.12-20150511.jar,lib/xmlbeans-2.6.0.jar
type:
Bundle-ClassPath: .,lib/poi-3.16.jar,lib/poi-ooxml-3.16.jar,lib/poi-oo
xml-schemas-3.16.jar,lib/xmlbeans-2.6.0.jar,lib/curvesapi-1.04.jar,lib/
commons-collections4-4.1.jar
Make sure that there are spaces at the beginning of the second and the third
line.
- - Save the changes, close the archiver, and rename
com.ibm.bi.core.poi_2.1.7.20170216.zip to
com.ibm.bi.core.poi_2.1.7.20170216.jar.
4. In the DataQuant for Workstation\plugins folder, rename
com.ibm.rsbi.textanalytics.doc_2.1.7.20170216.jar to
com.ibm.rsbi.textanalytics.doc_2.1.7.20170216.zip and open it in the archiver.
- - Remove everything from the "lib" folder.
- - Copy the
poi-3.16.jar,poi-ooxml-3.16.jar,poi-ooxml-schemas-3.16.jar,xmlbeans-2.6.0.jar
files into the "lib" folder.
- - Modify META-INF\MANIFEST-MF file. Instead of:
Bundle-ClassPath: .,lib/poi-3.12-20150511.jar,lib/poi-ooxml-3.12-20150
511.jar,lib/poi-ooxml-schemas-3.12-20150511.jar,lib/
poi-scratchpad-3.12-20150511.jar
type:
Bundle-ClassPath: .,lib/poi-3.16.jar,lib/poi-ooxml-3.16.jar,lib/poi-oo
xml-schemas-3.16.jar,lib/xmlbeans-2.6.0.jar
Make sure that there is a space at the beginning of the second line.
- -Save the changes, close the archiver, and rename
com.ibm.rsbi.textanalytics.doc_2.1.7.20170216.zip to
com.ibm.rsbi.textanalytics.doc_2.1.7.20170216.jar.
5. In the DataQuant for Workstation\plugins\
com.ibm.bi.thirdparty_2.1.7.20170216 folder
- - Remove commons-codec-1.6.jar and commons-logging-1.1.3.jar from the "Other"
folder.
- - Copy commons-codec-1.10.jar and commons-logging-1.2.jar into the the "Other"
folder.
- - Modify META-INF\MANIFEST.MF. Instead of:
Bundle-ClassPath: Other/mail.jar,Other/DPDFGen.jar,Other/js.jar,Other/
commons-logging-1.1.3.jar,Other/httpclient-4.3.1.jar,Other/httpcore-4
.3.jar,Other/commons-codec-1.6.jar,Other/pdfbox-1.7.0.jar,Other/fontb
ox-1.7.0.jar,Other/jackson-annotations-2.2.2.jar,Other/jackson-core-2
.2.2.jar,Other/jackson-databind-2.2.2.jar,Other/httpmime-4.3.jar
type:
Bundle-ClassPath: Other/mail.jar,Other/DPDFGen.jar,Other/js.jar,Other/
commons-logging-1.2.jar,Other/httpclient-4.3.1.jar,Other/httpcore-4.3
.jar,Other/commons-codec-1.10.jar,Other/pdfbox-1.7.0.jar,Other/fontbo
x-1.7.0.jar,Other/jackson-annotations-2.2.2.jar,Other/jackson-core-2.
2.2.jar,Other/jackson-databind-2.2.2.jar,Other/httpmime-4.3.jar
Make sure that there are spaces at the beginning of each line (with the
exception of the first line)
- - Save the changes.
6. Run Data Quant for Workstation with the following command line parameters:
dataquant.exe -clean -clearPersistedState
7. For DataQuant for WebSphere\DataQuantWebSphere21.war, rename
DataQuantWebSphere21.war to DataQuantWebSphere21.zip and open it in the file
archiver.
Make the changes described in steps #3 and #5 inside the
DataQuantWebSphere21.zip\WEB-INF\eclipse\plugins folder
or replace the existing com.ibm.bi.core.poi_2.1.7.20170216.jar and
com.ibm.bi.thirdparty_2.1.7.20170216 folders with the updated ones from the
workstation version.
- - Close file archiver.
- - Rename DataQuantWebSphere21.zip to DataQuantWebSphere21.war.
- - Redeploy DataQuantWebSphere21.war on your web server.
8. For DataQuant for WebSphere\DataQuantWebSphere21.ear, rename
DataQuantWebSphere21.ear to DataQuantWebSphere21.zip and open it in the file
archiver.
Make the changes described in step #7 for the DataQuantWebSphere21.war file
which is inside the DataQuantWebSphere21.zip archive, or replace the existing
DataQuantWebSphere21.war with the updated DataQuantWebSphere21.war from step #
7.
- - Close file archiver.
- - Rename DataQuantWebSphere21.zip to DataQuantWebSphere21.ear.
- - Redeploy DataQuantWebSphere21.ear on your web server.
Important note
IBM strongly suggests that all System z customers be subscribed to the System z
Security Portal to receive the latest critical System z security and integrity
service. If you are not subscribed, see the instructions on the System z
Security web site. Security and integrity APARs and associated fixes will be
posted to this portal. IBM suggests reviewing the CVSS scores and applying all
security or integrity fixes as soon as possible to minimize any potential risk.
*The CVSS Environment Score is customer environment specific and will
ultimately impact the Overall CVSS Score. Customers can evaluate the impact of
this vulnerability in their environments by accessing the links in the
Reference section of this Security Bulletin.
Disclaimer
According to the Forum of Incident Response and Security Teams (FIRST), the
Common Vulnerability Scoring System (CVSS) is an "industry open standard
designed to convey vulnerability severity and help to determine urgency and
priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF
ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY
ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
https://www.auscert.org.au/bulletins/
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iQIVAwUBWgpm+Ix+lLeg9Ub1AQhqLw/9F2Ni3oRkPBlwDzcAwjnS+/TN51EXo67p
wqqdP4P4XVGfNXfcfjoCJmQJDDb7+/fnB8QqjbGGhY30RXoowri/ZUfFbV4oGcNo
E9E0DIS7LNzQ2rnq/aOHd9A81v16ohxZNPOshTgAQncbj9GROLC48YWyPPCOkAoi
k+oLmV3VAJWsnvdeJyXyH0uZABDlkePDUMiPWFx1hdx0VDEANCfSZLGhqMZXcr2C
vAEx0Jm29makKETp8y+W29FXljeZVPdigi1BIfc+Dezgtiga3dlim8NFvXuM4rR1
8OiKyjLFQOOb0LtZT1G6k/6Uzb+hPcS+er2xSX+l+JOZ0Qy1wBoE2xQvc/jlAg4L
L04XMX9QRB3XjVhr99KlHd+qezTwl0imJHvdm5uUQScCWI9pCxz5wBXpTBzrVWtN
ClybV7IVF+7IH73UFFEAkPfLYxsI3P7MdOECWvrWAu5PTUCXcXVcM3bbMnfGYisn
p2frMpqoYoWMMMdDla2iYYFlx52DbDKjgb3kXFsCbb6sVoWo+HjkCnXn0wy79wsO
Y//ZP+jqylXeLJ2CsAu/Kcz6SR9yTMmcW2G9PXxCTVROZ8kTgji9ZhlbzdqKBwZh
j9OrR2uzPJik76eBUKPzqcIbEOmlM3Hnbv7lA2Pu1H/5vriFxKwwAa/M2Zvkj6tK
5ZfLshzGccg=
=TtSe
-----END PGP SIGNATURE-----