Hoary versions of Oracle's programming language Java can be a security nightmare for organizations and a fever dream for hackers because those older releases often contain flaws -- patched in later editions -- that remain susceptible to exploitation by bad actors now.
The problem with running a new version of Java is that some apps important to a business's operation may not work with it. Oracle made an effort to address that problem with a new version of Java 7 made available this week.
[ Think you know Java? Test your programming smarts in InfoWorld's Java IQ test. | Master the latest in Java development with our JavaWorld Enterprise Java newsletter. ]
The new release, Java Update 40, implements changes announced by Oracle earlier this year. They include allowing network administrators to create a DRS (Deployment Rule Set) that defines which version of Java an app should use. Such definitions could allow critical internal apps to use older versions of Java, while forcing external apps -- those more likely to carry infections that exploit flaws in older editions -- to use the latest version.
In a company blog, Java Platform Group Product Manager Erik Costlow explained that the new release of Java is aimed at desktop administrators who manage a number of users and need to control version compatibility and default dialogs to specific company applets. It's also designed for Java and Web Start app developers, who should be aware of the role deployment rule sets play on users' desktops.
[See also: Java security woes to stay with businesses for a long time]
While Oracle's intentions with DRS are laudable, the implementation may be wanting. "It's not going to be an easy fix for anybody," Ross Barrett, senior manager of security engineering at Rapid7, said in an interview. "It's better than nothing. We had nothing before and now we have something very complicated and hard to manage.
"It's a first step," he added. "Hopefully they'll refine it."
Oracle did not respond to a request for comment.
What DRS attempts to do is give organizations control over employees' desktop apps. That can be a dubious goal. "It's noble and a good idea, but it's high in administration costs," NSS Research Director Chris Morales said in an interview.
He explained that for DRS to work an organization will need to know about all of the applications on employee desktops and the versions of Java required by those apps. Then, each desktop has to be configured with that information and maintained.
"Those are all problems with application control in general that makes it not work well in a dynamic environment," Morales said.
Although DRS has security ramifications, it's more of a deployment tool than a security tool. "If you look at the configuration necessary to deploy this, it's really targeting large organizations that need to maintain a very consistent application environment across their infrastructure," Alex Watson, director of security research at Websense, said in an interview.
