After rushing out a Java update to address 50 security vulnerabilities back on Feb. 1, two weeks ahead of schedule, Oracle has acknowledged that the release missed some fixes and that it would issue an updated version of the February 2013 Critical Patch Update on the originally scheduled date.
The Redwood Shores, California-based software giant had originally accelerated the release of its Critical Patch Update due to the fact that a Java vulnerability was being actively exploited in the in the wild. While the move to rush a patch out the door should be commended, the company said that small number of fixes initially planned to be included in the February 2013 Critical Patch Update for Java SE were not included in the Feb. 1 patch release.
The updated February 2013 Critical Patch Update will be pushed out on Feb. 19, Oracle said.
“Note that Critical Patch Updates for Java SE are cumulative,” Oracle’s Eric Maurice explained in a blog post. “As a result, organizations that may not have applied the February 1st release will be able to apply the updated Critical Patch Update when it is published, and will then gain the benefit of all previously released Java SE fixes. As usual, desktop users will be able to install this new version from java.com or through the Java autoupdate.”
A recent advisory from US-CERT warned about previous and future vulnerabilities in Oracle’s Java software.
“These and previous Java vulnerabilities have been widely targeted by attackers, and new Java vulnerabilities are likely to be discovered. 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,” a Feb. 1 advisory from a US-CERT noted.
During a conference call with Java users and developers in late January, Milton Smith, Oracle’s head of Java security, acknowledged that Java’s ongoing security issues need to be addressed.
“The plan for Java security is really simple,” Smith said at the time. “It’s to get Java fixed up number one, and then number two, to communicate our efforts widely. We really can’t have one without the other… No amount of talking or smoothing over is going to make anybody happy or do anything for us. We have to fix Java.”