Security Update: Oracle Released Critical Patch to Address 40 Vulnerabilities Which Several Does Not Require Authentication to be Exploited

Status Type

Security Update

Date and Time

Tuesday, June 18, 2013 - 14:47


Security Update


Java Users

Oracle has released their June 2013 Critical Patch Update for Java SE to address 40 new security vulnerabilities of which 37 can be remotely exploitable without the need for a username and password.

Due to the threat posed by a successful attack, Oracle strongly recommends that customers apply CPU fixes as soon as possible.

Advanced Users: For a complete description of the vulnerability and updates, refer to Oracle Java SE Critical Patch Update Advisory - June 2013.

  • Web browsers using the Java 5, 6 or 7 plug-in are at high risk.

Java is a programming language that powers state-of-the-art programs including utilities, games, and business applications. Java runs on more than 850 million personal computers worldwide, and on billions of devices worldwide, including mobile and TV devices.
These and previous Java vulnerabilities have been widely targeted by attackers, and new Java vulnerabilities are likely to be discovered.
1.    Disable Java in web browsers

To defend against this and future Java vulnerabilities, consider disabling Java in web browsers until adequate updates have been installed. As with any software, unnecessary features should be disabled or removed as appropriate for your environment.
However, this is not always practical where Java-based Web applications are necessary for important operations.
Visit on how to disable Java.

2.    If you have a reason to use Java, here are a few options:

  • Use Google Chrome browser which automatically blocks Java and in cases where web pages tries to access Java, you will receive a message ““The Java plug-in needs your permission to run.” and you’ll be prompted to accept or deny.

3.    Update your software

  • If you have a computer support coordinator (CSC), no action on your part is required.

Note: Java 7 Update 17 sets the default Java security settings to "High" so that users will be prompted before running unsigned or self-signed Java applets.