Vulnerabilities / Threats
8/31/2012
12:06 PM
Connect Directly
RSS
E-Mail
50%
50%
Repost This

Security Experts: Java Should Be Disabled Unless Necessary

Security researchers say Java's popularity as an attack vector means it should be disabled unless it is needed

Since the acquisition of Sun Microsystems a few years ago, Oracle has found itself tasked with protecting a technology that has increasingly come under the gun from attackers -- Java. According to security researchers, Java's popularity as an attack vector means it's time for organizations to disable it unless there is a strong use case.

"As it happens, very few websites rely on Java for dynamic content," says Tod Beardsley, Metasploit engineering manager at Rapid7. "Java isn't relied on nearly as much as Javascript and Flash. Most people can disable their Java browser plug-in and not really notice the difference."

The bugs at the center of much of the latest drama are CVE-2012-4681, which Oracle patched Thursday amid growing anxiety. However, there is a report that researchers from security vendor Security Explorations have found a vulnerabilityin the update that can be exploited to escape the Java sandbox and execute code.

In any case, hackers had been targeting CVE-2012-4681 for at least the previous week, and had incorporated exploits for the bug into a number of exploit kits, including Black Hole, Sweet Orange, and others.

[ Hundreds of domains are serving up the latest Java attack, with tens of thousands of new victim machines since the exploit was added to the BlackHole toolkit. See New 'Reliable' Java Attack Spreading Fast, Uses Two Zero-Day Bugs. ]

"Just about all other kits on the black market use Java, Phoenix, Eleonore, RedKit, and Sakura are just a few examples," says Chris Astacio, manager of security research at Websense. "In fact, some kits use exclusively Java to attack clients. The reason for this is that Java provides the highest infection rate of all the other vulnerabilities used -- perhaps even two to three times more successful than the next most vulnerable application."

Like Beardsley, Astacio says that most people do not really need Java for day-to-day use, and that lack of need is the reason many in the security community suggests disabling or removing it -- though that can create issues of its own in some cases.

"If an organization removes it all together, they are increasing their security posture because that's one less vector to worry about attackers getting into their organization," he says. "The issue for some organizations with disabling Java is that they may have custom applications which use it. For this purpose, many in the security community have suggested using two browsers, one for day-to-day browsing, which has Java disabled, and another with Java enabled, but for the specific use of such applications that require it."

Besides CVE-2012-4681, the most commonly exploited Java vulnerabilities of late have been CVE-2012-1723 -- which was been very popular among the BlackHole crowd, and CVE-2012-0507, which is mostly known for its use in the Flashback attacks, Satnam Narang, security response manager at Symantec, tells Dark Reading. Both of those vulnerabilities have been patched by Oracle. If there is a use case for having Java installed, it is best to ensure that it is up-to-date, he said.

While Java users face some security challenges due to the software's popularity as an attack vector, Beardsley says he is very pleased with the speed of Oracle's reaction to the latest zero-day.

"Oracle has about a zillion clients all running various versions of their many software offerings, so patch deployment is understandably complicated for them," he says. "That said, it would be nice to see them on a more flexible once-a-month cycle like other major software vendors. It's painful to get there, but it's certainly possible."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-3946
Published: 2014-04-24
Cisco IOS before 15.3(2)S allows remote attackers to bypass interface ACL restrictions in opportunistic circumstances by sending IPv6 packets in an unspecified scenario in which expected packet drops do not occur for "a small percentage" of the packets, aka Bug ID CSCty73682.

CVE-2012-5723
Published: 2014-04-24
Cisco ASR 1000 devices with software before 3.8S, when BDI routing is enabled, allow remote attackers to cause a denial of service (device reload) via crafted (1) broadcast or (2) multicast ICMP packets with fragmentation, aka Bug ID CSCub55948.

CVE-2013-6738
Published: 2014-04-24
Cross-site scripting (XSS) vulnerability in IBM SmartCloud Analytics Log Analysis 1.1 and 1.2 before 1.2.0.0-CSI-SCALA-IF0003 allows remote attackers to inject arbitrary web script or HTML via an invalid query parameter in a response from an OAuth authorization endpoint.

CVE-2014-0188
Published: 2014-04-24
The openshift-origin-broker in Red Hat OpenShift Enterprise 2.0.5, 1.2.7, and earlier does not properly handle authentication requests from the remote-user auth plugin, which allows remote attackers to bypass authentication and impersonate arbitrary users via the X-Remote-User header in a request to...

CVE-2014-2391
Published: 2014-04-24
The password recovery service in Open-Xchange AppSuite before 7.2.2-rev20, 7.4.1 before 7.4.1-rev11, and 7.4.2 before 7.4.2-rev13 makes an improper decision about the sensitivity of a string representing a previously used but currently invalid password, which allows remote attackers to obtain potent...

Best of the Web