Oracle Java SE Critical Patch Update Advisory - June 2011


Description

A Critical Patch Update is a collection of patches for multiple security vulnerabilities. The Critical Patch Update for Java SE also includes non-security fixes. Critical Patch Updates are cumulative and each advisory describes only the security fixes added since the previous Critical Patch Update. Thus, prior Critical Patch Update Advisories should be reviewed for information regarding earlier accumulated security fixes. Please refer to:

Critical Patch Updates and Security Alerts for information about Oracle Security Advisories.


Due to the threat posed by a successful attack, Oracle strongly recommends that customers apply CPU fixes as soon as possible.
This Critical Patch Update contains 17 new security fixes across Java SE products.

Supported Products Affected

Security vulnerabilities addressed by this Critical Patch Update affect the products listed in the categories below.  Please click on the link in the Patch Availability column or in the Patch Availability Table to access the documentation for those patches.

Affected product releases and versions:

Java SEPatch Availability
JDK and JRE 6 Update 25 and earlierJava SE
JDK 5.0 Update 29 and earlierJava SE
SDK 1.4.2_31 and earlierJava SE

Patch Availability Table and Risk Matrix

Java SE fixes in this Update are cumulative; the latest Critical Patch Update includes all fixes from the previous Critical Patch Updates.

Patch Availability Table

Product GroupRisk MatrixPatch Availability and Installation Information
Java SEJava SE


Risk Matrix Content

The risk matrix lists only security vulnerabilities that are newly fixed by the patches associated with this advisory. Risk matrices for previous security fixes can be found in previous Critical Patch Update advisories.

Several vulnerabilities addressed in this Critical Patch Update affect multiple products.

Security vulnerabilities are scored using CVSS version 2.0 (see Oracle CVSS Scoring for an explanation of how Oracle applies CVSS 2.0). Oracle conducts an analysis of each security vulnerability addressed by a Critical Patch Update (CPU). Oracle does not disclose information about the security analysis, but the resulting Risk Matrix and associated documentation provide information about the type of vulnerability, the conditions required to exploit it, and the potential result of a successful exploit. Oracle provides this information, in part, so that customers may conduct their own risk analysis based on the particulars of their product usage. As a matter of policy, Oracle does not disclose detailed information about an exploit condition or results that can be used to conduct a successful exploit. Oracle will not provide additional information about the specifics of vulnerabilities beyond what is provided in the CPU or Security Alert notification, the Patch Availability Matrix, the readme files, and FAQs. Oracle does not provide advance notification on CPUs or Security Alerts to individual customers. Finally, Oracle does not distribute exploit code or “proof-of-concept” code for product vulnerabilities.

Workarounds

Due to the threat posed by a successful attack, Oracle strongly recommends that customers apply CPU fixes as soon as possible. Until you apply the CPU fixes, it may be possible to reduce the risk of successful attack by restricting network protocols required by an attack. For attacks that require certain privileges or access to certain packages, removing the privileges or the ability to access the packages from unprivileged users may help reduce the risk of successful attack. Both approaches may break application functionality, so Oracle strongly recommends that customers test changes on non-production systems. Neither approach should be considered a long-term solution as neither corrects the underlying problem.

Skipped Critical Patch Updates

Oracle strongly recommends that customers apply fixes as soon as possible. For customers that have skipped one or more Security advisories, please review previous advisories to determine appropriate actions.

Unsupported Products and De-Supported Versions

Unsupported products, releases and versions are not tested for the presence of vulnerabilities addressed by this Critical Patch Update. However, it is likely that earlier versions of affected releases are also affected by these vulnerabilities. Hence Oracle recommends that customers upgrade their Oracle products to a supported version.

Critical Patch Update patches are not provided for product versions that are no longer supported. We recommend that customers upgrade to the latest supported version of Oracle products in order to obtain patches.

Credit Statement

The following people or organizations reported security vulnerabilities addressed by this Critical Patch Update to Oracle: an Anonymous Reporter of TippingPoint's Zero Day Initiative; Aniway.Anyway via TippingPoint; binaryproof via iDefense; binaryproof via TippingPoint; Chris Ries via TippingPoint; Hisashi Kojima of Fujitsu Laboratories via JPCERT/CC; iDefense; Marc Schoenefeld of Red Hat; Peter Vreugdenhil of TippingPoint DVLabs; and Stephen Fewer of Harmony Security via TippingPoint.

Oracle Java SE Critical Patch Update Schedule

The next three dates for Oracle Java SE Critical Patch Updates are:

  • 18 October 2011
  • 14 February 2012
  • 12 June 2012

References


Modification History


DateComments
2011-June-07Rev 1. Initial Release

 



 

Appendix - Oracle Java SE

 

Oracle Java SE Executive Summary

 

This Critical Patch Update contains 17 new security fixes for Oracle Java SE - 5 apply to client and server deployments of Java SE, 11 apply to client deployments of Java SE only, and 1 applies to server deployments of Java SE only.  All of these vulnerabilities may be remotely exploitable without authentication, i.e., may be exploited over a network without the need for a username and password. 

CVSS scores below assume that a user running a Java applet or Java Web Start application has administrator privileges (typical on Windows). Where the user does not run with administrator privileges (typical on Solaris and Linux), the corresponding CVSS impact scores for Confidentiality, Integrity, and Availability are "Partial" instead of "Complete", and the corresponding CVSS Base score is 7.5 instead of 10 respectively.

For issues in Deployment, fixes are only made available for JDK and JRE 6. Users should use the Java Web Start in JRE 6 and the new Java Plug-in introduced in 6 Update 10.

 

My Oracle Support Note 360870.1 explains the impact of Java security vulnerabilities on Oracle products that include an Oracle Java SE JDK or JRE.

 

 

Oracle Java SE Risk Matrix


CVE#ComponentProtocolSub-
component
Remote Exploit without Auth.?CVSS VERSION 2.0 RISK (see Risk Matrix Definitions)Supported Versions AffectedNotes
Base ScoreAccess VectorAccess ComplexityAuthen-
tication
Confiden-
tiality
IntegrityAvail-
ability
CVE-2011-0862Java Runtime EnvironmentMultiple2DYes10.0NetworkLowNoneCompleteCompleteComplete6 Update 25 and before, 5.0 Update 29 and before, 1.4.2_31 and beforeSee Note 1
CVE-2011-0873Java Runtime EnvironmentMultiple2DYes10.0NetworkLowNoneCompleteCompleteComplete6 Update 25 and before, and 5.0 Update 29 and before See Note 2
CVE-2011-0815Java Runtime EnvironmentMultipleAWTYes10.0NetworkLowNoneCompleteCompleteComplete6 Update 25 and before, 5.0 Update 29 and before, 1.4.2_31 and beforeSee Note 3
CVE-2011-0817Java Runtime EnvironmentMultipleDeploymentYes10.0NetworkLowNoneCompleteCompleteComplete6 Update 25 and before on WindowsSee Note 3
CVE-2011-0863Java Runtime EnvironmentMultipleDeploymentYes10.0NetworkLowNoneCompleteCompleteComplete6 Update 25 and beforeSee Note 3
CVE-2011-0864Java Runtime EnvironmentMultipleHotSpotYes10.0NetworkLowNoneCompleteCompleteComplete6 Update 25 and before, 5.0 Update 29 and before, 1.4.2_31 and before See Note 3
CVE-2011-0802Java Runtime EnvironmentMultipleSoundYes10.0NetworkLowNoneCompleteCompleteComplete6 Update 25 and before, 5.0 Update 29 and before, 1.4.2_31 and beforeSee Note 2
CVE-2011-0814Java Runtime EnvironmentMultipleSoundYes10.0NetworkLowNoneCompleteCompleteComplete6 Update 25 and before, 5.0 Update 29 and before, 1.4.2_31 and before See Note 2
CVE-2011-0871Java Runtime EnvironmentMultipleSwingYes10.0NetworkLowNoneCompleteCompleteComplete6 Update 25 and before, 5.0 Update 29 and before, and 1.4.2_31 and beforeSee Note 3
CVE-2011-0786Java Runtime EnvironmentMultipleDeploymentYes7.6NetworkHighNoneCompleteCompleteComplete6 Update 25 and before on WindowsSee Note 3
CVE-2011-0788Java Runtime EnvironmentMultipleDeploymentYes7.6NetworkHighNoneCompleteCompleteComplete6 Update 25 and before on WindowsSee Note 3
CVE-2011-0866Java Runtime EnvironmentMultipleJava Runtime EnvironmentYes7.6NetworkHighNoneCompleteCompleteComplete6 Update 25 and before, 5.0 Update 29 and before, 1.4.2_31 and before on Windows See Note 3
CVE-2011-0868Java Runtime EnvironmentMultiple2DYes5.0NetworkLowNonePartialNoneNone6 Update 25 and beforeSee Note 2
CVE-2011-0872Java Runtime EnvironmentMultipleNIOYes5.0NetworkLowNoneNoneNonePartial+6 Update 25 and before, 5.0 Update 29 and before, 1.4.2_31 and before for Windows See Note 4
CVE-2011-0867Java Runtime EnvironmentMultipleNetworkingYes5.0NetworkLowNonePartialNoneNone6 Update 25 and before, 5.0 Update 29 and before, 1.4.2_31 and before See Note 3
CVE-2011-0869Java Runtime EnvironmentMultipleSAAJYes5.0NetworkLowNonePartialNoneNone6 Update 25 and beforeSee Note 3
CVE-2011-0865Java Runtime EnvironmentMultipleDeserializationYes2.6NetworkHighNoneNonePartialNone6 Update 25 and before, 5.0 Update 29 and before, 1.4.2_31 and before See Note 3
 

 

Notes:

  1. Fix addresses multiple instances of this vulnerability.
    Applies to client and server deployments of Java. This vulnerability can be exploited through Untrusted Java Web Start applications and Untrusted Java applets. It can also be exploited by supplying data to APIs in the specified Component without using untrusted Java Web Start applications or untrusted Java applets, such as through a web service.
  2. Applies to client and server deployments of Java. This vulnerability can be exploited through Untrusted Java Web Start applications and Untrusted Java applets. It can also be exploited by supplying data to APIs in the specified Component without using untrusted Java Web Start applications or untrusted Java applets, such as through a web service.
  3. Applies to client deployments of Java only. This vulnerability can be exploited only through Untrusted Java Web Start applications and Untrusted Java applets. (Untrusted Java Web Start applications and untrusted applets run in the Java sandbox with limited privileges.)
  4. Applies to server deployments of Java. This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service.