Featured Articles

HP Stream is a Chromebook killer priced at $200

HP Stream is a Chromebook killer priced at $200

We have been hearing reports of a new breed of affordable Windows notebooks for months. It is alleged that a number…

More...
AMD Radeon R7 SSD line-up goes official

AMD Radeon R7 SSD line-up goes official

AMD has officially launched its first ever SSDs and all three are part of AMD’s AMD Radeon R7 SSD series.

More...
KitKat has more than a fifth of Android users

KitKat has more than a fifth of Android users

Android 4.4 is now running on more than a fifth of Android devices, according to Google’s latest figures.

More...
Aerocool Dead Silence reviewed

Aerocool Dead Silence reviewed

Aerocool is well known for its gamer cases with aggressive styling. However, the Dead Silence chassis offers consumers a new choice,…

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

 

Facebook activity

Latest Commented Articles

Recent Comments