Oracle Java SE and Java for Business Critical Patch Update Advisory - October 2010


Description

A Critical Patch Update is a collection of patches for multiple security vulnerabilities. The Critical Patch Update for Java SE and Java for Business 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 29 new security fixes across Java SE and Java for Business 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 SE Patch Availability
JDK and JRE 6 Update 21 and earlier for Windows, Solaris, and Linux Java SE
JDK 5.0 Update 25 and earlier for Solaris Java SE
SDK 1.4.2_27 and earlier for Solaris Java SE
Java for Business Patch Availability
JDK and JRE 6 Update 21 and earlier for Windows, Solaris and Linux Java for Business
JDK and JRE 5.0 Update 25 and earlier for Windows, Solaris and Linux Java for Business
SDK and JRE 1.4.2_27 and earlier for Windows, Solaris and Linux Java for Business

Patch Availability Table and Risk Matrix

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

Patch Availability Table


Product Group Risk Matrix Patch Availability and Installation Information
Oracle Java SE and Java for Business Oracle Java SE and Java for Business Risk Matrix Oracle Java SE and Java for Business Critical Patch Update October 2010 My Oracle Support Note 1215628.1
Consumer users of Oracle Java SE can download the latest release from http://java.com. Users on the Windows platform can also use automatic updates to get the latest release


Risk Matrix Content

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; Berend-Jan Wever of Google; Chris Ries of Carnegie Mellon University; iDefense Security alias of iDefense; Intevydis via TippingPoint's Zero Day Initiative; Marc Schoenefeld of Red Hat; Marsh Ray of PhoneFactor; Matthias Kaiser (mka) via TippingPoint's Zero Day Initiative; Roberto Suggi Liverani of Security-Assessment.com; Shane Garrett of IBM X-Force; Stefano Di Paola of Minded Security; Stephen Fewer of Harmony Security via Tippingpoint; Steve Dispensa of PhoneFactor; Tavis Ormandy of Google; and Thomas Stehle.

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.

For this Critical Patch Update, Oracle recognizes Stefano Di Paola of Minded Security for contributions to Oracle's Security-In-Depth program.

Oracle Java SE and Java for Business Critical Patch Update Schedule

For the next calendar year, Oracle Java SE and Java for Business Critical Patch Updates will be released on the following dates:

  • 15 February 2011
  • 7 June 2011
  • 18 October 2011

References


Modification History


Date Comments
2010-October-12 Rev 1. Initial Release

 


 


Appendix - Oracle Java SE and Java for Business

 

Oracle Java SE and Java for Business Executive Summary


This Critical Patch Update contains 29 new security fixes for Oracle Java SE and Java for Business.  28 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 scores are 7.5, 6.8, and 5.1 instead of 10, 9.3, and 7.6 respectively.

My Oracle Support Note 360870.1 explains the impact of Java security vulnerabilities on Oracle products that include a JDK. 

 

Oracle Java SE and Java for Business Risk Matrix


CVE# Component Protocol Sub-
component
Remote Exploit without Auth.? CVSS VERSION 2.0 RISK (see Risk Matrix Definitions) Last Affected Patch set (per Supported Release) Notes
Base Score Access Vector Access Complexity Authen-
tication
Confiden-
tiality
Integrity Avail-
ability
CVE-2010-3556 2D Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21, 5.0 Update 25, 1.4.2_27, 1.3.1_28 See Note 1
CVE-2010-3562 2D Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21, 5.0 Update 25, 1.4.2_27, 1.3.1_28 See Note 2
CVE-2010-3565 2D Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21, 5.0 Update 25, 1.4.2_27 See Note 1
CVE-2010-3566 2D Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21, 5.0 Update 25 See Note 1
CVE-2010-3567 2D Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21, 5.0 Update 25 See Note 1
CVE-2010-3571 2D Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21, 5.0 Update 25, 1.4.2_27, 1.3.1_28 See Note 1
CVE-2010-3554 CORBA Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21, 5.0 Update 25, 1.4.2_27, 1.3.1_28 See Note 2
CVE-2010-3563 Deployment Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21 See Note 2
CVE-2010-3568 Java Runtime Environment Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21, 5.0 Update 25, 1.4.2_27 See Note 2
CVE-2010-3569 Java Runtime Environment Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21, 5.0 Update 25, 1.4.2_27 See Note 2
CVE-2010-3558 Java Web Start Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21 See Note 2
CVE-2010-3552 New Java Plug-in Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21 See Note 2
CVE-2010-3559 Sound Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21, 5.0 Update 25, 1.4.2_27, 1.3.1_28 See Note 1
CVE-2010-3572 Sound Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21, 5.0 Update 25, 1.4.2_27, 1.3.1_28 See Note 1
CVE-2010-3553 Swing Multiple - Yes 10.0 Network Low None Complete Complete Complete 6 Update 21, 5.0 Update 25, 1.4.2_27, 1.3.1_28 See Note 2
CVE-2010-3555 Deployment Multiple - Yes 9.3 Network Medium None Complete Complete Complete 6 Update 21 See Note 2
CVE-2010-3550 Java Web Start Multiple - Yes 9.3 Network Medium None Complete Complete Complete 6 Update 21, 5.0 Update 25 See Note 2
CVE-2010-3570 Deployment Toolkit Multiple - Yes 7.6 Network High None Complete Complete Complete 6 Update 21 See Note 2
CVE-2010-3561 CORBA Multiple - Yes 7.5 Network Low None Partial Partial Partial 6 Update 21, 5.0 Update 25 See Note 2
CVE-2009-3555 JSSE TLS/SSL - Yes 6.8 Network Medium None Partial Partial Partial 6 Update 21, 5.0 Update 25, 1.4.2_27 See Note 3
CVE-2010-1321 Kerberos Multiple - No 6.8 Network Low Single None None Complete 6 Update 21, 5.0 Update 25, 1.4.2_27 See Note 4
CVE-2010-3549 Networking Multiple - Yes 6.8 Network Medium None Partial Partial Partial 6 Update 21, 5.0 Update 25, 1.4.2_27, 1.3.1_28 See Note 2
CVE-2010-3557 Swing Multiple - Yes 6.8 Network Medium None Partial Partial Partial 6 Update 21, 5.0 Update 25, 1.4.2_27, 1.3.1_28 See Note 2
CVE-2010-3541 Networking Multiple - Yes 5.1 Network High None Partial Partial Partial 6 Update 21, 5.0 Update 25, 1.4.2_27, 1.3.1_28 See Note 2
CVE-2010-3573 Networking Multiple - Yes 5.1 Network High None Partial Partial Partial 6 Update 21, 5.0 Update 25 See Note 2
CVE-2010-3574 Networking Multiple - Yes 5.1 Network High None Partial Partial Partial 6 Update 21, 5.0 Update 25, 1.4.2_27, 1.3.1_28 See Note 2
CVE-2010-3548 JNDI Multiple - Yes 5.0 Network Low None Partial None None 6 Update 21, 5.0 Update 25, 1.4.2_27 See Note 2
CVE-2010-3551 Networking Multiple - Yes 5.0 Network Low None Partial None None 6 Update 21, 5.0 Update 25, 1.4.2_27 See Note 2
CVE-2010-3560 Networking Multiple - Yes 2.6 Network High None Partial None None 6 Update 21 See Note 2
 

 

Notes:

  1. May be vulnerable through untrusted Java Web Start applications and Java applets. May also be vulnerable, although highly unlikely, through processing untrusted data using APIs in the specified Component without using Java Web Start applications and Java applets.
  2. May be vulnerable only through untrusted Java Web Start applications and Java applets.
  3. Notes 1. and 2. are not applicable. See TLS Renegotiation Issue README.
  4. Notes 1. and 2. are not applicable. See MIT krb5 Security Advisory 2010-005.