Note:This Critical Patch Update includes all fixes provided in the Oracle Java SE Critical Patch Update February 2013, distributed on February 1, 2013, plus an additional five fixes which had been previously planned for delivery. This distribution therefore completes the content for all originally planned fixes to be included in the Java SE Critical Patch Update for February 2013. Note also that Oracle has scheduled a Java SE Critical Patch Update for April 16, 2013, in addition to those previously scheduled in June and October of 2013 and in January of 2014. This additional distribution will be used to further accelerate Java security fixes to Java users.
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 and Security Alert. Thus, prior Critical Patch Update and Security Alert 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 updated Critical Patch Update contains 5 additional security fixes across Java SE products. For more information about this updated release see https://blogs.oracle.com/security/.
Security vulnerabilities addressed by this updated 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.
Java SE fixes in this Update are cumulative; the latest Critical Patch Update includes all fixes from the previous Critical Patch Updates and Security Alerts (including Security Alert CVE-2013-0422).
|Product Group||Risk Matrix||Patch Availability and Installation Information|
|Oracle Java SE||Oracle JDK and JRE Risk Matrix||
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.
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.
Oracle strongly recommends that customers apply these 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, 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.
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.
The following people or organizations reported security vulnerabilities addressed by this Critical Patch Update to Oracle: Ben Murphy via TippingPoint; Kenny Paterson of Royal Holloway, University of London; Michael Schierl; Nadhem AlFardan of Royal Holloway, University of London; and Tomasko Labuda via the iSIGHT Partners GVP Program.
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 Will Dormann of CERT/CC for contributions to Oracle's Security-In-Depth program.
The next scheduled dates for Oracle Java SE Critical Patch Updates are:
|2013-February-19||Rev 1. Initial Release|
This updated Critical Patch Update contains 5 additional 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.
|CVE#||Component||Protocol||Sub- component||Remote Exploit without Auth.?||CVSS VERSION 2.0 RISK (see Risk Matrix Definitions)||Supported Versions Affected||Notes|
|Base Score||Access Vector||Access Complexity||Authen- tication||Confiden- tiality||Integrity||Avail- ability|
|CVE-2013-1487||Java Runtime Environment||Multiple||Deployment||Yes||10.0||Network||Low||None||Complete||Complete||Complete||7 Update 13 and before, 6 Update 39 and before||See Note 1|
|CVE-2013-1486||Java Runtime Environment||Multiple||JMX||Yes||10.0||Network||Low||None||Complete||Complete||Complete||7 Update 13 and before, 6 Update 39 and before, 5.0 Update 39 and before||See Note 1|
|CVE-2013-1484||Java Runtime Environment||Multiple||Libraries||Yes||10.0||Network||Low||None||Complete||Complete||Complete||7 Update 13 and before||See Note 1|
|CVE-2013-1485||Java Runtime Environment||Multiple||Libraries||Yes||5.0||Network||Low||None||None||Partial||None||7 Update 13 and before||See Note 1|
|CVE-2013-0169||Java Runtime Environment||SSL/TLS||JSSE||Yes||4.3||Network||Medium||None||Partial||None||None||7 Update 13 and before, 6 Update 39 and before, 5.0 Update 39 and before, 1.4.2_41 and before||See Note 2|