Critical CentOS java-1.8.0-openjdk Security Update
|java-1.8.0-openjdk-184.108.40.206-2.b15.el7_2.src.rpm, java-1.8.0-openjdk-220.127.116.11-2.b15.el7_2.x86_64.rpm, java-1.8.0-openjdk-accessibility-18.104.22.168-2.b15.el7_2.x86_64.rpm, java-1.8.0-openjdk-accessibility-debug-22.214.171.124-2.b15.el7_2.x86_64.rpm, java-1.8.0-openjdk-debug-126.96.36.199-2.b15.el7_2.x86_64.rpm, java-1.8.0-openjdk-demo-188.8.131.52-2.b15.el7_2.x86_64.rpm, java-1.8.0-openjdk-demo-debug-184.108.40.206-2.b15.el7_2.x86_64.rpm, java-1.8.0-openjdk-devel-220.127.116.11-2.b15.el7_2.x86_64.rpm, java-1.8.0-openjdk-devel-debug-18.104.22.168-2.b15.el7_2.x86_64.rpm, java-1.8.0-openjdk-headless-22.214.171.124-2.b15.el7_2.x86_64.rpm, java-1.8.0-openjdk-headless-debug-126.96.36.199-2.b15.el7_2.x86_64.rpm, java-1.8.0-openjdk-javadoc-188.8.131.52-2.b15.el7_2.noarch.rpm, java-1.8.0-openjdk-javadoc-debug-184.108.40.206-2.b15.el7_2.noarch.rpm, java-1.8.0-openjdk-src-220.127.116.11-2.b15.el7_2.x86_64.rpm, java-1.8.0-openjdk-src-debug-18.104.22.168-2.b15.el7_2.x86_64.rpm|
Updated java-1.8.0-openjdk packages that fix multiple security issues are
now available for Red Hat Enterprise Linux 7.
Red Hat Product Security has rated this update as having Critical security
impact. Common Vulnerability Scoring System (CVSS) base scores, which give
detailed severity ratings, are available for each vulnerability from the
CVE links in the References section.
The java-1.8.0-openjdk packages provide the OpenJDK 8 Java Runtime
Environment and the OpenJDK 8 Java Software Development Kit.
An out-of-bounds write flaw was found in the JPEG image format decoder in
the AWT component in OpenJDK. A specially crafted JPEG image could cause
a Java application to crash or, possibly execute arbitrary code. An
untrusted Java application or applet could use this flaw to bypass Java
sandbox restrictions. (CVE-2016-0483)
An integer signedness issue was found in the font parsing code in the 2D
component in OpenJDK. A specially crafted font file could possibly cause
the Java Virtual Machine to execute arbitrary code, allowing an untrusted
Java application or applet to bypass Java sandbox restrictions.
It was discovered that the password-based encryption (PBE) implementation
in the Libraries component in OpenJDK used an incorrect key length. This
could, in certain cases, lead to generation of keys that were weaker than
It was discovered that the JAXP component in OpenJDK did not properly
enforce the totalEntitySizeLimit limit. An attacker able to make a Java
application process a specially crafted XML file could use this flaw to
make 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 for
signing ServerKeyExchange and Client Authentication packets during a TLS
handshake. A man-in-the-middle attacker able to force a TLS connection to
use the MD5 hash function could use this flaw to conduct collision attacks
to impersonate a TLS server or an authenticated TLS client. (CVE-2015-7575)
Multiple flaws were discovered in the Networking and JMX components in
OpenJDK. An untrusted Java application or applet could use these flaws to
bypass certain Java sandbox restrictions. (CVE-2016-0402, CVE-2016-0448)
Note: If the web browser plug-in provided by the icedtea-web package was
installed, the issues exposed via Java applets could have been exploited
without user interaction if a user visited a malicious website.
Note: This update also disallows the use of the MD5 hash algorithm in the
certification path processing. The use of MD5 can be re-enabled by removing
MD5 from the jdk.certpath.disabledAlgorithms security property defined in
the java.security file.
All users of java-1.8.0-openjdk are advised to upgrade to these updated
packages, which resolve these issues. All running instances of OpenJDK Java
must be restarted for the update to take effect.
Please see https://www.redhat.com/footer/terms-of-use.html
Am I vulnerable?
The constraints below list the versions that this vulnerability is patched in, and versions that are unaffected. If a patch is ready but unrealeased, then it is pending.
Or, you can just let us figure it out for you! Appcanary continously monitor your installed packages, and tell you if any of them are vulnerable.Sign up for monitoring
Affected package information