Java update 13

[CyberNerd]

Another critical Java update.

I give it a week.

 

Java SE Downloads

 

Oracle Java SE Critical Patch Update Advisory - February 2013

 

Note: The original Critical Patch Update for Java SE – February 2013 was scheduled to be released on February 19th, but Oracle decided to accelerate the release of this Critical Patch Update because active exploitation “in the wild” of one of the vulnerabilities affecting the Java Runtime Environment (JRE) in desktop browsers, was addressed with this Critical Patch Update.

 

 

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 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 Critical Patch Update contains 50 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 SE Patch Availability

JDK and JRE 7 Update 11 and earlier Java SE

JDK and JRE 6 Update 38 and earlier Java SE

JDK and JRE 5.0 Update 38 and earlier Java SE

SDK and JRE 1.4.2_40 and earlier Java SE

JavaFX 2.2.4 and earlier JavaFX

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 and Security Alerts (including Security Alert CVE-2013-0422).

 

Patch Availability Table

Product Group Risk Matrix Patch Availability and Installation Information

Oracle Java SE Oracle JDK and JRE Risk Matrix

Oracle Java SE Critical Patch Update February 2013 My Oracle Support Note 1524383.1.

Developers can download the latest release from http://www.oracle.com/technetwork/java/javase/d ownloads/index.html.

Users running Java SE with a browser can download the latest release from java.com: Java + You. Users on the Windows platform can also use automatic updates to get the latest release.

Developers and users can download the latest Java FX release from External_BreadCrumb

 

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

 

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 Gowdiak of Security Explorations; Aniway.Anyway via TippingPoint; Chris Ries via TippingPoint; David Hoyt; David Thiel of Information Security Partners (iSEC); iDefense; James Forshaw (tyranid) via TippingPoint; Jeroen Frijters; Mark Yason of the IBM X-Force; Tomas Hoger of Red Hat; Vitaliy Toropov via iDefense; and Vitaliy Toropov via TippingPoint.

 

Oracle Java SE Critical Patch Update Schedule

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

 

18 June 2013

15 October 2013

14 January 2014

References

Oracle Critical Patch Updates and Security Alerts main page [ Oracle Technology Network ]

Oracle Critical Patch Updates and Security Alerts - Frequently Asked Questions [ CPU FAQ ]

Risk Matrix definitions [ Risk Matrix Definitions ]

Use of Common Vulnerability Scoring System (CVSS) by Oracle [ Oracle CVSS Scoring ]

English text version of risk matrices [ Oracle Technology Network ]

CVRF XML version of the risk matrix [ Oracle Technology Network ]

Previous Security Advisories for Java SE Security Updates [ Java Sun Alerts Archive Page ]

[SYNACK]

I think we can probably all agree that the benefits of running java are completely outweighed by its complete and utter lack of any working security at all.

[Arthur]

Does IBM make a JRE for Windows? If so, can't we all switch to that?

[CyberNerd]

Does IBM make a JRE for Windows? If so, can't we all switch to that?

 

first I've heard. There is an open source implementation - OpenJDK but I think it must suffer from the same problem, shortly after Oracle release an update my JBOSS machines autoupdate openJDK.

[Arthur]

After a bit of Googling I found the IBM JRE for Windows. It's bundled with the IBM Development Package for Eclipse. I'm not sure if it's any safer than Oracle's though.

 

http://i.imgur.com/mvZgQ4e.png

[Gatt]

Just tried to create an MST for Update 13 and this is what I'm seeing:

 

 

On the left is Update 13 - and on the right is Update 11.

 

In 13 there are no property references for settings any of the Automatic Updates, Java Updates, IEXplorer, Mozilla, properties