Java Runtime 1.8 U241 ((hot)) -

PDF download

Java Runtime 1.8 U241 ((hot)) -

Kyle Kingsbury
2016-07-12

In the last Jepsen analysis, we found that RethinkDB could lose data when a network partition occurred during cluster reconfiguration. In this analysis, we’ll show that although VoltDB 6.3 claims strict serializability, internal optimizations and bugs lead to stale reads, dirty reads, and even lost updates. Fixes are now available in version 6.4. This work was funded by VoltDB, and conducted in accordance with the Jepsen ethics policy.

Java Runtime 1.8 U241 ((hot)) -

Java Runtime Environment (JRE) 1.8 Update 241

Introduction

The Java Runtime Environment (JRE) 1.8 Update 241, commonly referred to as Java 8u241, is a significant update to the Java 8 line, which was initially released in March 2014. This update includes various security enhancements, bug fixes, and improvements.

This release established the security baseline for the Java 8 family at the time of its debut. IANA Time Zone Data: Includes version for updated global time zone rules. Key Features & Enhancements Enhanced SASL Mechanism Control: A new security property, jdk.sasl.disabledMechanisms java runtime 1.8 u241

-Djdk.serialFilter=!*

3.2 Bug Fixes (Selected)

  • JDK-8236730 – Fix for XML Signature validation issue with certain canonicalization methods.
  • JDK-8235385 – Support for com.sun.net.httpserver to handle HEAD requests correctly.
  • JDK-8230419 – Improved handling of ZoneId for historical dates.
  • JDK-8230000 – Fix for javax.crypto.Cipher performance regression introduced in earlier updates.
  • JDK-8233228 – Disabled weak cipher suites (e.g., 3DES_EDE_CBC) by default in Oracle JSSE.

Security: Update 241 is over six years old. Modern versions include many more security patches. Java Runtime Environment (JRE) 1

  • High Severity Vulnerabilities: Fixes included vulnerabilities in the Libraries, Security, and Hotspot components.
  • Notable CVEs: The release patched CVEs (Common Vulnerabilities and Exposures) with high CVSS scores. Without this update, systems running previous versions (e.g., 8u231) were susceptible to malicious code execution via untrusted data deserialization or crafted network packets.