RHSA-2016:0050: Important: java-1.8.0-openjdk security update

Published Jan 20, 2016
·
Updated

The java-1.8.0-openjdk packages provide the OpenJDK 8 Java RuntimeEnvironment and the OpenJDK 8 Java Software Development Kit.An out-of-bounds write flaw was found in the JPEG image format decoder inthe AWT component in OpenJDK. A specially crafted JPEG image could causea Java application to crash or, possibly execute arbitrary code. Anuntrusted Java application or applet could use this flaw to bypass Javasandbox restrictions. (CVE-2016-0483)An integer signedness issue was found in the font parsing code in the 2Dcomponent in OpenJDK. A specially crafted font file could possibly causethe Java Virtual Machine to execute arbitrary code, allowing an untrustedJava application or applet to bypass Java sandbox restrictions.(CVE-2016-0494)It was discovered that the password-based encryption (PBE) implementationin the Libraries component in OpenJDK used an incorrect key length. Thiscould, in certain cases, lead to generation of keys that were weaker thanexpected. (CVE-2016-0475)It was discovered that the JAXP component in OpenJDK did not properlyenforce the totalEntitySizeLimit limit. An attacker able to make a Javaapplication process a specially crafted XML file could use this flaw tomake the application consume an excessive amount of memory. (CVE-2016-0466)A flaw was found in the way TLS 1.2 could use the MD5 hash function forsigning ServerKeyExchange and Client Authentication packets during a TLShandshake. A man-in-the-middle attacker able to force a TLS connection touse the MD5 hash function could use this flaw to conduct collision attacksto impersonate a TLS server or an authenticated TLS client. (CVE-2015-7575)Multiple flaws were discovered in the Networking and JMX components inOpenJDK. An untrusted Java application or applet could use these flaws tobypass certain Java sandbox restrictions. (CVE-2016-0402, CVE-2016-0448)Note: This update also disallows the use of the MD5 hash algorithm in thecertification path processing. The use of MD5 can be re-enabled by removingMD5 from the jdk.certpath.disabledAlgorithms security property defined inthe java.security file.All users of java-1.8.0-openjdk are advised to upgrade to these updatedpackages, which resolve these issues. All running instances of OpenJDK Javamust be restarted for the update to take effect.

Affected Software

24 affected componentsFixes available
redhat/java<1.8.0-openjdk-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-debug-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-debug-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-debuginfo-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-debuginfo-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-demo-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-demo-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-demo-debug-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-demo-debug-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-devel-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-devel-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-devel-debug-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-devel-debug-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-headless-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-headless-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-headless-debug-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-headless-debug-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-javadoc-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-javadoc-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-javadoc-debug-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-javadoc-debug-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-src-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-src-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-src-debug-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-src-debug-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-debug-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-debug-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-debuginfo-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-debuginfo-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-demo-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-demo-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-demo-debug-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-demo-debug-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-devel-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-devel-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-devel-debug-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-devel-debug-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-headless-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-headless-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-headless-debug-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-headless-debug-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-src-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-src-1.8.0.71-1.b15.el6_7
redhat/java<1.8.0-openjdk-src-debug-1.8.0.71-1.b15.el6_7
1.8.0-openjdk-src-debug-1.8.0.71-1.b15.el6_7

Remediation

Event History

Jan 20, 2016
Advisory Published
12:00 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of RHSA-2016:0050?

RHSA-2016:0050 is classified as a critical security vulnerability due to the potential for remote code execution.

2

How do I fix RHSA-2016:0050?

To fix RHSA-2016:0050, update to the latest version of the affected OpenJDK packages, specifically 1.8.0-openjdk-1.8.0.71-1.b15.el6_7.

3

What systems are affected by RHSA-2016:0050?

RHSA-2016:0050 affects systems running the specified versions of OpenJDK 8 distributed by Red Hat.

4

What is the impact of exploiting RHSA-2016:0050?

Exploiting RHSA-2016:0050 could allow an attacker to execute arbitrary code on the affected system, potentially leading to a complete compromise.

5

Are there any workarounds for RHSA-2016:0050?

There are no official workarounds for RHSA-2016:0050; the recommended action is to apply the available updates.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203