Updated java-1.8.0-openjdk packages fix security vulnerabilities
Publication date: 30 Jul 2017Modification date: 30 Jul 2017
Type: security
Affected Mageia releases : 5 , 6
CVE: CVE-2017-10053 , CVE-2017-10067 , CVE-2017-10074 , CVE-2017-10078 , CVE-2017-10081 , CVE-2017-10087 , CVE-2017-10089 , CVE-2017-10090 , CVE-2017-10096 , CVE-2017-10101 , CVE-2017-10102 , CVE-2017-10107 , CVE-2017-10108 , CVE-2017-10109 , CVE-2017-10110 , CVE-2017-10111 , CVE-2017-10115 , CVE-2017-10116 , CVE-2017-10135 , CVE-2017-10193 , CVE-2017-10198
Description
It was discovered that the DCG implementation in the RMI component of OpenJDK failed to correctly handle references. A remote attacker could possibly use this flaw to execute arbitrary code with the privileges of RMI registry or a Java RMI application (CVE-2017-10102). Multiple flaws were discovered in the RMI, JAXP, ImageIO, Libraries, AWT, Hotspot, and Security components in OpenJDK. An untrusted Java application or applet could use these flaws to completely bypass Java sandbox restrictions (CVE-2017-10107, CVE-2017-10096, CVE-2017-10101, CVE-2017-10089, CVE-2017-10090, CVE-2017-10087, CVE-2017-10111, CVE-2017-10110, CVE-2017-10074, CVE-2017-10067). It was discovered that the LDAPCertStore class in the Security component of OpenJDK followed LDAP referrals to arbitrary URLs. A specially crafted LDAP referral URL could cause LDAPCertStore to communicate with non-LDAP servers (CVE-2017-10116). It was discovered that the Nashorn JavaScript engine in the Scripting component of OpenJDK could allow scripts to access Java APIs even when access to Java APIs was disabled. An untrusted JavaScript executed by Nashorn could use this flaw to bypass intended restrictions (CVE-2017-10078). It was discovered that the Security component of OpenJDK could fail to properly enforce restrictions defined for processing of X.509 certificate chains. A remote attacker could possibly use this flaw to make Java accept certificate using one of the disabled algorithms (CVE-2017-10198). A covert timing channel flaw was found in the DSA implementation in the JCE component of OpenJDK. A remote attacker able to make a Java application generate DSA signatures on demand could possibly use this flaw to extract certain information about the used key via a timing side channel (CVE-2017-10115). A covert timing channel flaw was found in the PKCS#8 implementation in the JCE component of OpenJDK. A remote attacker able to make a Java application repeatedly compare PKCS#8 key against an attacker controlled value could possibly use this flaw to determine the key via a timing side channel (CVE-2017-10135). It was discovered that the BasicAttribute and CodeSource classes in OpenJDK did not limit the amount of memory allocated when creating object instances from a serialized form. A specially crafted serialized input stream could cause Java to consume an excessive amount of memory (CVE-2017-10108, CVE-2017-10109). Multiple flaws were found in the Hotspot and Security components in OpenJDK. An untrusted Java application or applet could use these flaws to bypass certain Java sandbox restrictions (CVE-2017-10081, CVE-2017-10193). It was discovered that the JPEGImageReader implementation in the 2D component of OpenJDK would, in certain cases, read all image data even if it was not used later. A specially crafted image could cause a Java application to temporarily use an excessive amount of CPU and memory (CVE-2017-10053).
References
- https://bugs.mageia.org/show_bug.cgi?id=21324
- http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html
- https://rhn.redhat.com/errata/RHSA-2017-1789.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/thread/NDHUFK52KRCLSHVSLH4Y7B4HJHXZYXRV/
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10053
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10067
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10074
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10078
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10081
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10087
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10089
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10090
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10096
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10101
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10102
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10107
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10108
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10109
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10110
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10111
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10115
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10116
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10135
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10193
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10198
SRPMS
5/core
- java-1.8.0-openjdk-1.8.0.141-1.b16.1.mga5
- copy-jdk-configs-2.3-1.mga5
6/core
- java-1.8.0-openjdk-1.8.0.141-1.b16.1.mga6
- copy-jdk-configs-2.3-1.mga6