Featured Articles

Snapdragon 400 is Qualcomm’s SoC for watches, wearables

Snapdragon 400 is Qualcomm’s SoC for watches, wearables

We wanted to learn a bit more about Qualcomm's plans for wearables and it turns out that the company believes its…

More...
Qualcomm sampling 20nm Snapdragon 810

Qualcomm sampling 20nm Snapdragon 810

We had a chance to talk to Michelle Leyden-Li, Senior Director of Marketing, QCT at Qualcomm and get an update on…

More...
EVGA GTX 970 SC ACX 2.0 reviewed

EVGA GTX 970 SC ACX 2.0 reviewed

Nvidia has released two new graphics cards based on its latest Maxwell GPU architecture. The Geforce GTX 970 and Geforce GTX…

More...
Nvidia GTX 980 reviewed

Nvidia GTX 980 reviewed

Nvidia has released two new graphics cards based on its latest Maxwell GPU architecture. The Geforce GTX 970 and Geforce GTX…

More...
PowerColor TurboDuo R9 285 reviewed

PowerColor TurboDuo R9 285 reviewed

Today we will take a look at the PowerColor TurboDuo Radeon R9 285. The card is based on AMD’s new…

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