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 thePatch Availability Table to access the documentation for those patches.

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.

Modification History

Date

Comments

2011-June-07

Rev 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.

6 Update 25 and before, 5.0 Update 29 and before, and 1.4.2_31 and before

See Note 3

CVE-2011-0786

Java Runtime Environment

Multiple

Deployment

Yes

7.6

Network

High

None

Complete

Complete

Complete

6 Update 25 and before on Windows

See Note 3

CVE-2011-0788

Java Runtime Environment

Multiple

Deployment

Yes

7.6

Network

High

None

Complete

Complete

Complete

6 Update 25 and before on Windows

See Note 3

CVE-2011-0866

Java Runtime Environment

Multiple

Java Runtime Environment

Yes

7.6

Network

High

None

Complete

Complete

Complete

6 Update 25 and before, 5.0 Update 29 and before, 1.4.2_31 and before on Windows

See Note 3

CVE-2011-0868

Java Runtime Environment

Multiple

2D

Yes

5.0

Network

Low

None

Partial

None

None

6 Update 25 and before

See Note 2

CVE-2011-0872

Java Runtime Environment

Multiple

NIO

Yes

5.0

Network

Low

None

None

None

Partial+

6 Update 25 and before, 5.0 Update 29 and before, 1.4.2_31 and before for Windows

See Note 4

CVE-2011-0867

Java Runtime Environment

Multiple

Networking

Yes

5.0

Network

Low

None

Partial

None

None

6 Update 25 and before, 5.0 Update 29 and before, 1.4.2_31 and before

See Note 3

CVE-2011-0869

Java Runtime Environment

Multiple

SAAJ

Yes

5.0

Network

Low

None

Partial

None

None

6 Update 25 and before

See Note 3

CVE-2011-0865

Java Runtime Environment

Multiple

Deserialization

Yes

2.6

Network

High

None

None

Partial

None

6 Update 25 and before, 5.0 Update 29 and before, 1.4.2_31 and before

See Note 3

Notes:

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.

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.

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.)

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.