VUPEN Security Research - Sun Java JDK/JRE AWT Library Invalid Pointer Vulnerability
"Java is a programming language and computing platform released by Sun Microsystems. It is the underlying technology that powers state-of-the-art programs including utilities, games, and business applications.
Java runs on more than 850 million personal computers worldwide, and on billions of devices worldwide, including mobile and TV devices."
VUPEN Vulnerability Research Team discovered a vulnerability in Sun Java JDK/JRE.
The flaw is caused by an invalid pointer within the AWT (Abstract Windowing Toolkit) library when processing data passed to a specific function, which could be exploited by attackers to execute arbitrary code by tricking a user into visiting a specially crafted web page.
Sun Java JDK version 6 Update 18 and prior Sun Java JDK version 5.0 Update 23 and prior Sun Java JRE version 6 Update 18 and prior Sun Java JRE version 5.0 Update 23 and prior Sun Java JRE version 1.4.2_25 and prior Sun Java SDK version 1.4.2_25 and prior
In-depth binary analysis of the vulnerability and a proof-of-concept have been released by VUPEN through the VUPEN Binary Analysis & Exploits Service :
Upgrade to Sun Java JDK and JRE 6 Update 19, JDK and JRE 5.0 Update 24, and JRE and SDK version 1.4.2_26 : http://www.oracle.com/technology/deploy/security/critical-patch-updates/javacpumar2010.html
The vulnerability was discovered by Alexandre Pelletier of VUPEN Security
VUPEN is a leading IT security research company providing vulnerability management and security intelligence solutions which enable enterprises and institutions to eliminate vulnerabilities before they can be exploited, ensure security policy compliance and meaningfully measure and manage risks.
Governmental and federal agencies, and global enterprises in the financial services, insurance, manufacturing and technology industries rely on VUPEN to improve their security, prioritize resources, cut time and costs, and stay ahead of the latest threats.
2009-11-20 - Vendor notified 2009-11-24 - Vendor response 2010-01-09 - Status update received 2010-03-03 - Status update received 2010-03-31 - Coordinated public Disclosure