Bug 1273645 - (CVE-2015-4911) CVE-2015-4911 OpenJDK: incomplete supportDTD enforcement (JAXP, 8130078)
CVE-2015-4911 OpenJDK: incomplete supportDTD enforcement (JAXP, 8130078)
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20151020,repor...
: Security
Depends On: 1278650 1278653 1298015
Blocks: 1257667 1278635
  Show dependency treegraph
 
Reported: 2015-10-20 16:55 EDT by Tomas Hoger
Modified: 2016-01-13 23:25 EST (History)
23 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-01-13 23:11:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tomas Hoger 2015-10-20 16:55:25 EDT
It was discovered that the StAX XML parser in the JAXP component of OpenJDK could do certain DTD processing even when DTD support was disabled via the javax.xml.stream.supportDTD system property.  A specially crafted XML document could cause a Java application using JAXP to consume an excessive amount of memory and CPU time when parsed.
Comment 1 Tomas Hoger 2015-10-21 04:55:54 EDT
Public now via Oracle Critical Patch Update - October 2015.  Fixed in Oracle Java SE 6u105, 7u91, and 8u65.

External References:

http://www.oracle.com/technetwork/topics/security/cpuoct2015-2367953.html#AppendixJAVA
Comment 2 errata-xmlrpc 2015-10-21 14:49:02 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 5

Via RHSA-2015:1921 https://rhn.redhat.com/errata/RHSA-2015-1921.html
Comment 3 errata-xmlrpc 2015-10-21 17:00:13 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6
  Red Hat Enterprise Linux 7

Via RHSA-2015:1920 https://rhn.redhat.com/errata/RHSA-2015-1920.html
Comment 4 errata-xmlrpc 2015-10-21 17:10:01 EDT
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6
  Red Hat Enterprise Linux 7

Via RHSA-2015:1919 https://rhn.redhat.com/errata/RHSA-2015-1919.html
Comment 5 errata-xmlrpc 2015-10-22 14:36:01 EDT
This issue has been addressed in the following products:

  Oracle Java for Red Hat Enterprise Linux 7
  Oracle Java for Red Hat Enterprise Linux 5
  Oracle Java for Red Hat Enterprise Linux 6

Via RHSA-2015:1928 https://rhn.redhat.com/errata/RHSA-2015-1928.html
Comment 6 errata-xmlrpc 2015-10-22 14:37:06 EDT
This issue has been addressed in the following products:

  Oracle Java for Red Hat Enterprise Linux 7
  Oracle Java for Red Hat Enterprise Linux 6

Via RHSA-2015:1926 https://rhn.redhat.com/errata/RHSA-2015-1926.html
Comment 7 errata-xmlrpc 2015-10-22 14:46:51 EDT
This issue has been addressed in the following products:

  Oracle Java for Red Hat Enterprise Linux 7
  Oracle Java for Red Hat Enterprise Linux 5
  Oracle Java for Red Hat Enterprise Linux 6

Via RHSA-2015:1927 https://rhn.redhat.com/errata/RHSA-2015-1927.html
Comment 8 Tomas Hoger 2015-10-26 10:38:48 EDT
OpenJDK8 upstream commit:

http://hg.openjdk.java.net/jdk8u/jdk8u/jaxp/rev/f98b8f06a46a
Comment 10 Jason Shepherd 2015-11-06 00:46:20 EST
While this issue affects the JAXP libraries used by EAP, it's possible to
override them with the patched ones from the JDK using the instructions
in this article:

   https://access.redhat.com/solutions/874723
Comment 11 errata-xmlrpc 2015-11-18 11:42:20 EST
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 5
  Red Hat Enterprise Linux 6
  Red Hat Enterprise Linux 7

Via RHSA-2015:2086 https://rhn.redhat.com/errata/RHSA-2015-2086.html
Comment 16 Jason Shepherd 2016-01-13 23:22:06 EST
Closed the EAP trackers as won't fix because the issue was ranked as moderate and there is a workaround. The workaround is to use your own JAXP libraries by packaging them with your application.

   https://access.redhat.com/solutions/874723

Note You need to log in before you can comment on or make changes to this bug.