CVE Vulnerabilities


Improper Restriction of XML External Entity Reference

Published: Feb 01, 2017 | Modified: Feb 08, 2017
CVSS 3.x
CVSS 2.x
7.5 HIGH

IBM InfoSphere Information Server is vulnerable to a denial of service, caused by an XML External Entity Injection (XXE) error when processing XML data. A remote attacker could exploit this vulnerability to expose highly sensitive information or consume all available memory resources.


The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

Affected Software

Name Vendor Start Version End Version
Infosphere_datastage Ibm 11.3 11.3
Infosphere_datastage Ibm 11.3.1 11.3.1
Infosphere_datastage Ibm 11.5 11.5
Infosphere_information_server Ibm 11.3 11.3
Infosphere_information_server Ibm 11.3.1 11.3.1
Infosphere_information_server Ibm 11.5 11.5
Infosphere_information_server_on_cloud Ibm 11.5 11.5

Extended Description

XML documents optionally contain a Document Type Definition (DTD), which, among other features, enables the definition of XML entities. It is possible to define an entity by providing a substitution string in the form of a URI. The XML parser can access the contents of this URI and embed these contents back into the XML document for further processing. By submitting an XML file that defines an external entity with a file:// URI, an attacker can cause the processing application to read the contents of a local file. For example, a URI such as “file:///c:/winnt/win.ini” designates (in Windows) the file C:\Winnt\win.ini, or file:///etc/passwd designates the password file in Unix-based systems. Using URIs with other schemes such as http://, the attacker can force the application to make outgoing requests to servers that the attacker cannot reach directly, which can be used to bypass firewall restrictions or hide the source of attacks such as port scanning. Once the content of the URI is read, it is fed back into the application that is processing the XML. This application may echo back the data (e.g. in an error message), thereby exposing the file contents.

Potential Mitigations