Featured Articles

IHS teardown reveals Galaxy S5 BOM

IHS teardown reveals Galaxy S5 BOM

Research firm IHS got hold of Samsung’s new flagship smartphone and took it apart to the last bolt to figure out…

More...
Galaxy S5, HTC One M8 available selling well

Galaxy S5, HTC One M8 available selling well

Samsung’s Galaxy S5 has finally gone on sale and it can be yours for €699, which is quite a lot of…

More...
Intel lists Haswell refresh parts

Intel lists Haswell refresh parts

Intel has added a load of Haswell refresh parts to its official price list and there really aren’t any surprises to…

More...
Respawn confirms Titanfall DLC for May

Respawn confirms Titanfall DLC for May

During his appearance at PAX East panel and confirmed on Twitter, Titanfall developer Respawn confirmed that the first DLC pack for…

More...
KFA2 GTX 780 Ti Hall Of Fame reviewed

KFA2 GTX 780 Ti Hall Of Fame reviewed

KFA2 gained a lot of overclocking experience with the GTX 780 Hall of Fame (HOF), which we had a chance to…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Friday, 19 July 2013 10:01

Oracle’s Java security commitment questioned

Written by Nick Farrell

Not bothering to check vulnerabilities

Oracle has been accused of ignoring security holes in its Java software. Security Explorations researcher Adam Gowdiak claimed that Oracle has not bothered to check against a "very classic attack" that he has found against the software.

Gowdiak has not released the details of the vulnerability, but did state that it is related to the new Reflection API that was introduced into Java SE 7, and that successful exploitation allows an attacker to reliably bypass Java's security sandbox. But what is weird is that the attack has been in the public knowledge for at least 10+ years.

“It's one of those risks one should protect against in the first place, when new features are added to Java at the core VM level," Gowdiak wrote on Bugtraq.

Gowdiak claims that his company's proof-of-concept code works on the most recent version of Java SE 7, Update 25 and earlier. Gowdiak questioned how seriously Oracle is taking security, given he believed that the flaw should have been picked up rather easily.

He argued that its security assurance procedures, if they existed, should have quickly identified the issue and eliminated it before Java SE 7 was released.

Nick Farrell

E-mail: This e-mail address is being protected from spambots. You need JavaScript enabled to view it
blog comments powered by Disqus

To be able to post comments please log-in with Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments