April 2013 Critical Patch Update for Java SE Released
by Carol~ - 4/16/13 11:20 PM
From: The Oracle Software Security Assurance Blog
Eric P. Maurice on Apr 16, 2013
Oracle today released two Critical Patch Updates: the April 2013 Critical Patch Update and the April 2013 Critical Patch Update for Java SE. The previous blog entry provided a summary of the April 2013 Critical Patch Update, and this entry will discuss the content of the Critical Patch Update for Java SE.
The April 2013 Critical Patch Update for Java SE provides 42 new security fixes. 39 of the vulnerabilities fixed in this Critical Patch Update are remotely exploitable without authentication. The maximum CVSS Base Score for these vulnerabilities is 10.0, and this score affect 19 different vulnerabilities.
Out of the 42 vulnerabilities, only 2 can affect server deployments of Java. Server exploitation can only occur as a result of these bugs when malicious data is supplied into specific APIs on the server (e.g., through a web service), and one of these bugs actually require local access to be exploited.
As usual, Oracle recommends that this Critical Patch Update be applied as soon as possible. Desktop users can install this new version from java.com or through the Java Autoupdate
For More Information:
The advisory for the April 2013 Critical Patch Update for Java SE is located at http://www.oracle.com/technetwork/topics/security/javacpuapr2013-1928497.html.
⇒ ⇒ NOTE: The offline installer/s can be found here:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
From the SANS ISC: Java 7 Update 21 is available - Watch for Behaviour Changes !
Several of our readers have written in to let us know about the latest Java Update.
So why isn't this a normal one-liner with a pointer off to the readme? Because Oracle has significantly changed how Java runs with this version. Java now requires code signing, and will pop up brightly coloured dialogue boxes if your code is not signed. They now alert on unsigned, signed-but-expired and self-signed certificates.
We'll even need to click "OK" when we try to download and execute signed and trusted Java.
This is a really positive move on their part - with as many problems as Java has, it'll be nice to stop blaming the developers of the language entirely for malicious code - Java doesn't give you malware, running malware gives you malware.
(not that Java is perfect, mind you)
The graphics you can expect to see once you update are:
[Screenshot: Valid Certificate] - [Screenshot: Self-Signed Certificate]
[Screenshot:Expired Certificate] - [Screenshot: Unsigned Application]
Full details on the new run policy can be found here ==> https://www.java.com/en/download/help/appsecuritydialogs.xml
And more information can be found here ==> http://www.oracle.com/technetwork/java/javase/tech/java-code-signing-1915323.html