Oracle Java SE Critical Patch Update Advisory - February 2012


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 14 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 7 Update 2 and earlierJava SE
JDK and JRE 6 Update 30 and earlierJava SE
JDK and JRE 5.0 Update 33 and earlierJava SE
SDK and JRE 1.4.2_35 and earlierJava SE
JavaFX 2.0.2 and earlierJavaFX

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
Oracle Java SEOracle JDK and JRE 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.

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 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: Alin Rad Pop (binaryproof) via Tipping Point's Zero Day Initiative; an Anonymous Reporter via iDefense; an Anonymous Reporter of TippingPoint's Zero Day Initiative; TELUS Security Labs; Chris Ries via TippingPoint; Doug Lea of OSWEGO State University of New York; Jeroen Frijters; Peter Vreugdenhil of TippingPoint DVLabs; and Timo Warns of PRESENSE Technologies.

Security-In-Depth Contributors

Oracle provides recognition to people that have contributed to our Security-In-Depth program (see FAQ). People are recognized for Security-In- Depth contributions if they provide information, observations or suggestions pertaining to security vulnerability issues that result in significant modification of Oracle code or documentation in future releases, but are not of such a critical nature that they are distributed in Critical Patch Updates.

In this Critical Patch Update Advisory, Oracle recognizes Chris Ries via TippingPoint for contributions to Oracle's Security-In-Depth program.

Oracle Java SE Critical Patch Update Schedule

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

  • 12 June 2012
  • 16 October 2012
  • 19 February 2013

References


Modification History


DateComments
2012-May-17Rev 3. Updated CVSS score for CVE-2012-0507
2012-February-17Rev 2. Replaced CVE-2011-3571 with CVE-2012-0507
2012-February-14Rev 1. Initial Release

 



 

Appendix - Oracle Java SE

 

Oracle Java SE Executive Summary

 

This Critical Patch Update contains 14 new security fixes for Oracle Java SE.  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.  The English text form of this Risk Matrix can be found here.

The CVSS scores below assume that a user running a Java applet or Java Web Start application has administrator privileges (typical on Windows). When 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 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-2012-0497Java Runtime EnvironmentMultiple2DYes10.0NetworkLowNoneCompleteCompleteComplete7 Update 2 and before, 6 Update 30 and beforeSee Note 1
CVE-2012-0498Java Runtime EnvironmentMultiple2DYes10.0NetworkLowNoneCompleteCompleteComplete7 Update 2 and before, 6 Update 30 and before, 5.0 Update 33 and beforeSee Note 1
CVE-2012-0499Java Runtime EnvironmentMultiple2DYes10.0NetworkLowNoneCompleteCompleteComplete7 Update 2 and before, 6 Update 30 and before, 5.0 Update 33 and before, 1.4.2_35 and before.
JavaFX 2.0.2 and before
See Note 1
CVE-2012-0507Java Runtime EnvironmentMultipleConcurrencyYes10.0NetworkLowNoneCompleteCompleteComplete7 Update 2 and before, 6 Update 30 and before, 5.0 Update 33 and beforeSee Note 2
CVE-2012-0500Java Runtime EnvironmentMultipleDeploymentYes10.0NetworkLowNoneCompleteCompleteComplete7 Update 2 and before, 6 Update 30 and before.
JavaFX 2.0.2 and before
See Note 2
CVE-2012-0508JavaFXMultiple-Yes10.0NetworkLowNoneCompleteCompleteCompleteJavaFX 1.3.0 and before, 1.2.2 and beforeSee Note 3
CVE-2012-0504Java Runtime EnvironmentMultipleInstallYes9.3NetworkMediumNoneCompleteCompleteComplete7 Update 2 and before, 6 Update 30 and beforeSee Note 4
CVE-2012-0503Java Runtime EnvironmentMultipleI18nYes7.5NetworkLowNonePartialPartialPartial7 Update 2 and before, 6 Update 30 and before, 5.0 Update 33 and before, 1.4.2_35 and beforeSee Note 2
CVE-2012-0505Java Runtime EnvironmentMultipleSerializationYes7.5NetworkLowNonePartialPartialPartial7 Update 2 and before, 6 Update 30 and before, 5 Update 33 and before, 1.4.2_35 and beforeSee Note 2
CVE-2012-0502Java Runtime EnvironmentMultipleAWTYes6.4NetworkLowNonePartialNonePartial7 Update 2 and before, 6 Update 30 and before, 5.0 Update 33 and before, 1.4.2_35 and beforeSee Note 2
CVE-2011-3563Java Runtime EnvironmentMultipleSoundYes6.4NetworkLowNonePartialNonePartial7 Update 2 and before, 6 Update 30 and before, 5.0 Update 33 and before, 1.4.2_35 and beforeSee Note 1
CVE-2011-5035Java Runtime EnvironmentHTTPLightweight HTTP ServerYes5.0NetworkLowNoneNoneNonePartial+7 Update 2 and before, 6 Update 30 and beforeSee Note 5
CVE-2012-0501Java Runtime EnvironmentMultipleJava Runtime EnvironmentYes5.0NetworkLowNoneNoneNonePartial7 Update 2 and before, 6 Update 30 and before, 5.0 Update 33 and beforeSee Note 1
CVE-2012-0506Java Runtime EnvironmentMultipleCORBAYes4.3NetworkMediumNoneNonePartialNone7 Update 2 and before, 6 Update 30 and before, 5.0 Update 33 and before, 1.4.2_35 and beforeSee Note 2
 

 

Notes:

  1. 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 deployments of Java. 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.)
  3. Applies to client deployments of Java.
  4. Applies to client deployments of Java. This vulnerability is in the Java Update mechanism.
  5. The Lightweight HTTP server is used by JAX- WS.