An untrusted library search path flaw was found in the JCE component ofOpenJDK. A local attacker could possibly use this flaw to cause a Javaapplication using JCE to load an attacker-controlled library and hence escalatetheir privileges. It was found that the JAXP component of OpenJDK failed to correctly enforceparse tree size limits when parsing XML document. An attacker able to make aJava application parse a specially crafted XML document could use this flaw tomake it consume an excessive amount of CPU and memory. It was discovered that the HTTP client implementation in the Networkingcomponent of OpenJDK could cache and re-use an NTLM authenticated connection ina different security context. A remote attacker could possibly use this flaw tomake a Java application perform HTTP requests authenticated with credentials ofa different user. It was discovered that the Security component of OpenJDK did not allow usersto restrict the set of algorithms allowed for Jar integrity verification. Thisflaw could allow an attacker to modify content of the Jar file that used weaksigning key or hash algorithm. Newline injection flaws were discovered in FTP and SMTP client implementationsin the Networking component in OpenJDK. A remote attacker could possibly usethese flaws to manipulate FTP or SMTP connections established by a Javaapplication. Note: This update adds support for the "jdk.ntlm.cache" system property which,when set to false, prevents caching of NTLM connections and authentications andhence prevents this issue. However, caching remains enabled by default.Note: This updates extends the fix for CVE-2016-5542 released as part of theRHSA-2016-2658 erratum to no longer allow the MD5 hash algorithm during the Jarintegrity verification by adding it to the jdk.jar.disabledAlgorithms securityproperty.