.
/v3-uk/news/1970224/new-java-exploits-brewing
12 Jan 2007, Shaun Nichols , V3
Attackers have released exploit code targeting two previously patched flaws in Sun Microsystems' Java Runtime Environment (JRE) and Java Software Development Kit (SDK).
The flaws could allow an attacker to remotely execute code on a Windows, Linux or Solaris system. Sun issued patches for both vulnerabilities in December.
The JRE component allows JavaScript code to be executed on most operating systems, including Windows, Mac OS, Linux and Unix.
The vulnerabilities affect JRE 1.3.x, 1.4.x and 1.5.x, as well as versions 1.3.x and 1.4.x of the SDK and versions 1.5.x of the Java Development Kit.
Danish security vendor Secunia rates one of the vulnerabilities as 'highly critical', the company's second-highest level, owing to the possibility for remote code execution.
Eric Sites, vice president of research and development at Sunbelt Software, told vnunet.com that, although exploits against Java vulnerabilities are uncommon, they do still pop up.
"Sun has been very thorough and steady in the stuff it implements and how fast it implements it," he said.
Sites pointed out that Java is inherently a more secure system, because JRE uses so-called sandboxing that allows it to operate as a virtual machine to block access to other parts of the system.
He warned, however, that as developers create JavaScript applications that require more capabilities, they begin to call up .dll files from the system.
As soon as the programs reach outside the virtual machine for system files, the security protection of the sandbox is negated.
Sites said that this latest exploit is particularly worrying, as the code could be embedded in a small Java application that launches from a browser window and could deliver a malicious payload very quickly.
Do you agree?
Worthless article
This news article provides no reference numbers to the alleged vulnerability, so you cannot find something that sounds like this JRE problem. There were 47 vulnerabilities reported in 2006 to JRE, and none in 2007, so this daily report 2 weeks into the new year must be referring to something weeks old at best. This report does not even cite the date of the Secunia report, so the problem cannot be tracked that way. Who are we helping with this report? What were we supposed to do?
Posted by Anonymous Coward, 16 Jan 2007