RHSA-2016:1840HighCVSS 7.6

Red Hat Security Advisory: eap7-jboss-ec2-eap security, bug fix, and enhancement update

Published
September 8, 2016
Last Modified
November 5, 2026

🔗 CVE IDs covered (3)

CVE-2016-4993 →CVE-2016-5406 →CVE-2015-0254 →

📋 Description

CVE-2015-0254 — jakarta-taglibs-standard: XXE and RCE via XSL extension in JSTL XML tags CVE-2016-4993 — eap: HTTP header injection / response splitting CVE-2016-5406 — EAP7 Privilege escalation when managing domain including earlier version slaves

🎯 Affected products8

  • Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 6 Server
  • Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 7 Server
  • eap7-jboss-ec2-eap-0:7.0.2-2.GA_redhat_1.ep7.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 6 Server
  • eap7-jboss-ec2-eap-0:7.0.2-2.GA_redhat_1.ep7.el6.src as a component of Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 6 Server
  • eap7-jboss-ec2-eap-0:7.0.2-2.GA_redhat_1.ep7.el7.noarch as a component of Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 7 Server
  • eap7-jboss-ec2-eap-0:7.0.2-2.GA_redhat_1.ep7.el7.src as a component of Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 7 Server
  • eap7-jboss-ec2-eap-samples-0:7.0.2-2.GA_redhat_1.ep7.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 6 Server
  • eap7-jboss-ec2-eap-samples-0:7.0.2-2.GA_redhat_1.ep7.el7.noarch as a component of Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 7 Server

✅ Remediation

Before applying this update, back up your existing Red Hat JBoss Enterprise Application Platform installation and deployed applications. For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The JBoss server process must be restarted for the update to take effect. Workaround: Users should upgrade to Apache Standard Taglibs 1.2.3 or later. This version uses JAXP’s FEATURE_SECURE_PROCESSING to restrict XML processing. Depending on the Java runtime version in use, additional configuration may be required: Java8: External entity access is automatically disabled if a SecurityManager is active. Java7: JAXP properties may need to be used to disable external access. See http://docs.oracle.com/javase/tutorial/jaxp/properties/properties.html Java6 and earlier: A new system property org.apache.taglibs.standard.xml.accessExternalEntity may be used to specify the protocols that can be used to access external entities. This defaults to "all" if no SecurityManager is present and to "" (thereby disabling access) if a SecurityManager is detected.

🔗 References (9)