Security Holes In Google's Android SDK
Redon Buckeye writes "Google's Android software development kit is using several outdated and vulnerable open-source image processing libraries, some of which can be exploited to take complete control of mobile devices running the Android platform. From the article: 'Several vulnerabilities have been found in Android's core libraries for processing graphic content in some of the most used image formats (PNG, GIF, and BMP). While some of these vulnerabilities stem from the use of outdated and vulnerable open source image-processing libraries, other were introduced by native Android code that uses them or that implements new functionality.'"
He was referring to Android, not the libraries. :-/
Javascript + Nintendo DSi = DSiCade
For this type of problem? You bet your horse it is. Buffer overflow problems are so 1970's. Can we please move on?
Javascript + Nintendo DSi = DSiCade
This is already fixed in m5-rc15 which was released yesterday...
"I told you a million times not to exaggerate!"
anybody who read the bugtraq submission of the flaws would no that google themselves responded with a comment that they knew they were using old version of the libraries adn that they were planning on updating them in the next release.
They also pointed out that this iss not BETA code, but merely a release of propsed code to allow potential devlopers to add their insights to the project on which direction the code should go on various portions.
The libraries have now been replaced (evidently) with the newer ones, which probably doens't mean a damn thing as there are no currently available public platforms running the software and won't be for a while.
calling this dumb is a bit overkill.