Oracle Java SE Critical Patch Update Advisory - October 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 20 new security fixes across Java SE, of which 6 are applicable to JRockit.

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 7Java SE
JDK and JRE 6 Update 27 and earlierJava SE
JDK and JRE 5.0 Update 31 and earlierJava SE
SDK and JRE 1.4.2_33 and earlierJava SE
JavaFX 2.0JavaFX
JRockit R28.1.4 and earlier (JDK and JRE 6 and 5.0)JRockit

Patch Availability Table and Risk Matrix

Java SE and JRockit 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
Oracle Java SEOracle JDK, JRE and JRockit Risk Matrix


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 Document, 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 Critical Patch Update 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: Adam Barth; axtaxt viaTipping Point's Zero Day Initiative; Eric Rescorla; Juliano Rizzo; Michael Schierl via Tipping Point; Neal Poole; Roee Hay of IBM Rational Application Security Research Group; Sami Koivu via Tipping Point's Zero Day Initiative; Thai Duong; and Yair Amit of IBM Rational Application Security Research Group.

Oracle Java SE Critical Patch Update Schedule

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

  • 14 February 2012
  • 12 June 2012
  • 16 October 2012

References


Modification History


DateComments
2011-October-18Rev 1. Initial Release

 



Appendix - Oracle Java SE

 

Oracle Java SE Executive Summary


This Critical Patch Update contains 20 new security fixes for Oracle Java SE.  19 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", lowering the CVSS Base Score. For example, a Base Score of 10.0 becomes 7.5.

For issues in Deployment, fixes are only made available for JDK and JRE 7 and 6. Users should use the default Java Plug-in and Java Web Start in the latest JDK and JRE 7 or 6 releases.

 

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 JDK, JRE and JRockit 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-3548Java Runtime EnvironmentMultipleAWTYes10.0NetworkLowNoneCompleteCompleteCompleteJDK and JRE 7, 6 Update 27 and before, 5.0 Update 31 and before, 1.4.2_33 and beforeSee Note 1
CVE-2011-3521Java Runtime EnvironmentMultipleDeserializationYes10.0NetworkLowNoneCompleteCompleteCompleteJDK and JRE 7, 6 Update 27 and before, 5.0 Update 31 and beforeSee Note 1
CVE-2011-3554Java Runtime EnvironmentMultipleJava Runtime EnvironmentYes10.0NetworkLowNoneCompleteCompleteCompleteJDK and JRE 7, 6 Update 27 and before, 5.0 Update 31 and beforeSee Note 1
CVE-2011-3544Java Runtime EnvironmentMultipleScriptingYes10.0NetworkLowNoneCompleteCompleteCompleteJDK and JRE 7, 6 Update 27 and beforeSee Note 1
CVE-2011-3545Java Runtime EnvironmentMultipleSoundYes10.0NetworkLowNoneCompleteCompleteCompleteJDK and JRE 6 Update 27 and before, 5.0 Update 31 and before, 1.4.2_33 and before.
JRockit R28.1.4 and before
See Note 2
CVE-2011-3549Java Runtime EnvironmentMultipleSwingYes10.0NetworkLowNoneCompleteCompleteCompleteJDK and JRE 6 Update 27 and before, 5.0 Update 31 and before, 1.4.2_33 and beforeSee Note 1
CVE-2011-3551Java Runtime EnvironmentMultiple2DYes9.3NetworkMediumNoneCompleteCompleteCompleteJDK and JRE 7, 6 Update 27 and before.
JRockit R28.1.4 and before
See Note 2
CVE-2011-3550Java Runtime EnvironmentMultipleAWTYes7.6NetworkHighNoneCompleteCompleteCompleteJDK and JRE 7, 6 Update 27 and beforeSee Note 1
CVE-2011-3516Java Runtime EnvironmentMultipleDeploymentYes7.6NetworkHighNoneCompleteCompleteCompleteJDK and JRE 6 Update 27 and before on WindowsSee Note 1
CVE-2011-3556Java Runtime EnvironmentMultipleRMIYes7.5NetworkLowNonePartialPartialPartialJDK and JRE 7, 6 Update 27 and before, 5.0 Update 31 and before, 1.4.2_33 and before.
JRockit R28.1.4 and before
See Note 3
CVE-2011-3557Java Runtime EnvironmentMultipleRMIYes6.8NetworkMediumNonePartialPartialPartialJDK and JRE 7, 6 Update 27 and before, 5.0 Update 31 and before, 1.4.2_33 and before.
JRockit R28.1.4 and before
See Note 3
CVE-2011-3560Java Runtime EnvironmentSSL/TLSJSSEYes6.4NetworkLowNonePartialPartialNoneJDK and JRE 7, 6 Update 27 and before, 5.0 Update 31 and before, 1.4.2_33 and beforeSee Note 1
CVE-2011-3555Java Runtime EnvironmentMultipleJava Runtime EnvironmentYes6.1NetworkHighNoneNonePartialCompleteJDK and JRE 7See Note 1
CVE-2011-3546Java Runtime EnvironmentMultipleDeploymentYes5.8NetworkMediumNonePartialPartialNoneJDK and JRE 7, 6 Update 27 and before.
JavaFX 2.0
See Note 1
CVE-2011-3558Java Runtime EnvironmentMultipleHotSpotYes5.0NetworkLowNonePartialNoneNoneJDK and JRE 7, 6 Update 27 and beforeSee Note 1
CVE-2011-3547Java Runtime EnvironmentMultipleNetworkingYes5.0NetworkLowNonePartialNoneNoneJDK and JRE 7, 6 Update 27 and before, 5.0 Update 31 and before, 1.4.2_33 and beforeSee Note 1
CVE-2011-3389Java Runtime EnvironmentSSL/TLSJSSEYes4.3NetworkMediumNonePartialNoneNoneJDK and JRE 7, 6 Update 27 and before, 5.0 Update 31 and before, 1.4.2_33 and before.
JRockit R28.1.4 and before
See Note 4
CVE-2011-3553Java Runtime EnvironmentMultipleJAXWSNo3.5NetworkMediumSinglePartialNoneNoneJDK and JRE 7, 6 Update 27 and before.
JRockit R28.1.4 and before
See Note 5
CVE-2011-3552Java Runtime EnvironmentMultipleNetworkingYes2.6NetworkHighNoneNonePartialNoneJDK and JRE 7, 6 Update 27 and before, 5.0 Update 31 and before, 1.4.2_33 and beforeSee Note 1
CVE-2011-3561Java Runtime EnvironmentMultipleDeploymentYes1.8Adjacent NetworkHighNonePartialNoneNoneJDK and JRE 7, 6 Update 27 and before.
JavaFX 2.0
See Note 1
 

 

Notes:

  1. 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.)
  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 RMI server deployments of Java.
  4. This is a vulnerability in the SSLv3/TLS 1.0 protocol. Exploitation of this vulnerability requires a man-in-the-middle and the attacker needs to be able to inject chosen plaintext.
  5. Applies to server deployments of Java. This vulnerability can only be exploited by supplying data to APIs in the specified Component, such as through a web service. It cannot be exploited through Untrusted Java Web Start applications or Untrusted Java applets.