Vulnerability Details : CVE-2016-6059
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.
Vulnerability category: XML external entity (XXE) injectionDenial of service
Products affected by CVE-2016-6059
- cpe:2.3:a:ibm:infosphere_information_server:11.3:*:*:*:*:*:*:*
- cpe:2.3:a:ibm:infosphere_information_server:11.3.1:*:*:*:*:*:*:*
- cpe:2.3:a:ibm:infosphere_information_server:11.5:*:*:*:*:*:*:*
- cpe:2.3:a:ibm:infosphere_datastage:11.3:*:*:*:*:*:*:*
- cpe:2.3:a:ibm:infosphere_datastage:11.3.1:*:*:*:*:*:*:*
- cpe:2.3:a:ibm:infosphere_datastage:11.5:*:*:*:*:*:*:*
- cpe:2.3:a:ibm:infosphere_information_server_on_cloud:11.5:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2016-6059
0.36%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 55 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2016-6059
Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
---|---|---|---|---|---|---|
7.5
|
HIGH | AV:N/AC:L/Au:S/C:P/I:N/A:C |
8.0
|
7.8
|
NIST | |
8.1
|
HIGH | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
2.8
|
5.2
|
NIST |
CWE ids for CVE-2016-6059
-
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.Assigned by: nvd@nist.gov (Primary)
References for CVE-2016-6059
-
http://www.securityfocus.com/bid/94032
IBM InfoSphere Information Server CVE-2016-6059 XML External Entity Injection VulnerabilityTechnical Description;VDB Entry
-
http://www.ibm.com/support/docview.wss?uid=swg21991683
IBM Security Bulletin: InfoSphere Information Server is vulnerable to XML External Entity Injection (XXE) (CVE-2016-6059)Patch;Vendor Advisory
Jump to