Critical CentOS java-1.6.0-openjdk Update
|java-1.6.0-openjdk-220.127.116.11-18.104.22.168.5.el6_3.i686.rpm, java-1.6.0-openjdk-22.214.171.124-126.96.36.199.5.el6_3.src.rpm, java-1.6.0-openjdk-188.8.131.52-184.108.40.206.5.el6_3.x86_64.rpm, java-1.6.0-openjdk-demo-220.127.116.11-18.104.22.168.5.el6_3.i686.rpm, java-1.6.0-openjdk-demo-22.214.171.124-126.96.36.199.5.el6_3.x86_64.rpm, java-1.6.0-openjdk-devel-188.8.131.52-184.108.40.206.5.el6_3.i686.rpm, java-1.6.0-openjdk-devel-220.127.116.11-18.104.22.168.5.el6_3.x86_64.rpm, java-1.6.0-openjdk-javadoc-22.214.171.124-126.96.36.199.5.el6_3.i686.rpm, java-1.6.0-openjdk-javadoc-188.8.131.52-184.108.40.206.5.el6_3.x86_64.rpm, java-1.6.0-openjdk-src-220.127.116.11-18.104.22.168.5.el6_3.i686.rpm, java-1.6.0-openjdk-src-22.214.171.124-126.96.36.199.5.el6_3.x86_64.rpm|
Updated java-1.6.0-openjdk packages that fix several security issues are
now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team 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.
These packages provide the OpenJDK 6 Java Runtime Environment and the
OpenJDK 6 Software Development Kit.
Multiple improper permission check issues were discovered in the Beans,
Swing, and JMX components in OpenJDK. An untrusted Java application or
applet could use these flaws to bypass Java sandbox restrictions.
(CVE-2012-5086, CVE-2012-5084, CVE-2012-5089)
Multiple improper permission check issues were discovered in the Scripting,
JMX, Concurrency, Libraries, and Security components in OpenJDK. An
untrusted Java application or applet could use these flaws to bypass
certain Java sandbox restrictions. (CVE-2012-5068, CVE-2012-5071,
CVE-2012-5069, CVE-2012-5073, CVE-2012-5072)
It was discovered that java.util.ServiceLoader could create an instance of
an incompatible class while performing provider lookup. An untrusted Java
application or applet could use this flaw to bypass certain Java sandbox
It was discovered that the Java Secure Socket Extension (JSSE) SSL/TLS
implementation did not properly handle handshake records containing an
overly large data length value. An unauthenticated, remote attacker could
possibly use this flaw to cause an SSL/TLS server to terminate with an
It was discovered that the JMX component in OpenJDK could perform certain
actions in an insecure manner. An untrusted Java application or applet
could possibly use this flaw to disclose sensitive information.
A bug in the Java HotSpot Virtual Machine optimization code could cause it
to not perform array initialization in certain cases. An untrusted Java
application or applet could use this flaw to disclose portions of the
virtual machine's memory. (CVE-2012-4416)
It was discovered that the SecureRandom class did not properly protect
against the creation of multiple seeders. An untrusted Java application or
applet could possibly use this flaw to disclose sensitive information.
It was discovered that the java.io.FilePermission class exposed the hash
code of the canonicalized path name. An untrusted Java application or
applet could possibly use this flaw to determine certain system paths, such
as the current working directory. (CVE-2012-3216)
This update disables Gopher protocol support in the java.net package by
default. Gopher support can be enabled by setting the newly introduced
property, "jdk.net.registerGopherProtocol", to true. (CVE-2012-5085)
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.
This erratum also upgrades the OpenJDK package to IcedTea6 1.11.5. Refer to
the NEWS file, linked to in the References, for further information.
All users of java-1.6.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