Critical CentOS java-1.7.0-openjdk Update
|java-1.7.0-openjdk-220.127.116.11-18.104.22.168.el6_5.i686.rpm, java-1.7.0-openjdk-22.214.171.124-126.96.36.199.el6_5.src.rpm, java-1.7.0-openjdk-188.8.131.52-184.108.40.206.el6_5.x86_64.rpm, java-1.7.0-openjdk-220.127.116.11-18.104.22.168.el7_0.src.rpm, java-1.7.0-openjdk-22.214.171.124-126.96.36.199.el7_0.x86_64.rpm, java-1.7.0-openjdk-accessibility-188.8.131.52-184.108.40.206.el7_0.x86_64.rpm, java-1.7.0-openjdk-demo-220.127.116.11-18.104.22.168.el6_5.i686.rpm, java-1.7.0-openjdk-demo-22.214.171.124-126.96.36.199.el6_5.x86_64.rpm, java-1.7.0-openjdk-demo-188.8.131.52-184.108.40.206.el7_0.x86_64.rpm, java-1.7.0-openjdk-devel-220.127.116.11-18.104.22.168.el6_5.i686.rpm, java-1.7.0-openjdk-devel-22.214.171.124-126.96.36.199.el6_5.x86_64.rpm, java-1.7.0-openjdk-devel-188.8.131.52-184.108.40.206.el7_0.x86_64.rpm, java-1.7.0-openjdk-headless-220.127.116.11-18.104.22.168.el7_0.x86_64.rpm, java-1.7.0-openjdk-javadoc-22.214.171.124-126.96.36.199.el6_5.noarch.rpm, java-1.7.0-openjdk-javadoc-188.8.131.52-184.108.40.206.el7_0.noarch.rpm, java-1.7.0-openjdk-src-220.127.116.11-18.104.22.168.el6_5.i686.rpm, java-1.7.0-openjdk-src-22.214.171.124-126.96.36.199.el6_5.x86_64.rpm, java-1.7.0-openjdk-src-188.8.131.52-184.108.40.206.el7_0.x86_64.rpm|
|rhn.redhat.com, lists.centos.org, lists.centos.org|
Updated java-1.7.0-openjdk packages that fix multiple security issues are
now available for Red Hat Enterprise Linux 6 and 7.
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.
The java-1.7.0-openjdk packages provide the OpenJDK 7 Java Runtime
Environment and the OpenJDK 7 Java Software Development Kit.
It was discovered that the Hotspot component in OpenJDK did not properly
verify bytecode from the class files. An untrusted Java application or
applet could possibly use these flaws to bypass Java sandbox restrictions.
A format string flaw was discovered in the Hotspot component event logger
in OpenJDK. An untrusted Java application or applet could use this flaw to
crash the Java Virtual Machine or, potentially, execute arbitrary code with
the privileges of the Java Virtual Machine. (CVE-2014-2490)
Multiple improper permission check issues were discovered in the Libraries
component in OpenJDK. An untrusted Java application or applet could use
these flaws to bypass Java sandbox restrictions. (CVE-2014-4223,
Multiple flaws were discovered in the JMX, Libraries, Security, and
Serviceability components in OpenJDK. An untrusted Java application or
applet could use these flaws to bypass certain Java sandbox restrictions.
(CVE-2014-4209, CVE-2014-4218, CVE-2014-4221, CVE-2014-4252, CVE-2014-4266)
It was discovered that the RSA algorithm in the Security component in
OpenJDK did not sufficiently perform blinding while performing operations
that were using private keys. An attacker able to measure timing
differences of those operations could possibly leak information about the
used keys. (CVE-2014-4244)
The Diffie-Hellman (DH) key exchange algorithm implementation in the
Security component in OpenJDK failed to validate public DH parameters
properly. This could cause OpenJDK to accept and use weak parameters,
allowing an attacker to recover the negotiated key. (CVE-2014-4263)
The CVE-2014-4262 issue was discovered by Florian Weimer of Red Hat
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.
All users of java-1.7.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