First published: Wed Mar 12 2014(Updated: )
Florian Weimer discovered that AtomicReferenceFieldUpdater in OpenJDK does not properly check if the field to be updated is of primitive type. An untrusted Java application or applet could use flaw to trigger Java virtual machine memory corruption and possibly bypass Java sandbox restrictions. AtomicReferenceFieldUpdater API documentation: <a href="http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/atomic/AtomicReferenceFieldUpdater.html">http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/atomic/AtomicReferenceFieldUpdater.html</a> This issue is mitigated by the bug that prevents Atomic*FieldUpdater instances when code runs under security manager restrictions under OpenJDK and Oracle JDK 6 and 7. The bug was fixed in JDK8: <a href="http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7103570">http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7103570</a> <a href="http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7131655">http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7131655</a> <a href="http://hg.openjdk.java.net/jdk8/tl/jdk/rev/48513d156965">http://hg.openjdk.java.net/jdk8/tl/jdk/rev/48513d156965</a> Acknowledgement: This issue was discovered by Florian Weimer of Red Hat Product Security.
Credit: secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
Oracle JDK | =1.5.0-update65 | |
Oracle JDK | =1.6.0-update75 | |
Oracle JDK | =1.7.0-update60 | |
Oracle JDK | =1.8.0-update5 | |
Oracle JRE | =1.5.0-update65 | |
Oracle JRE | =1.6.0-update75 | |
Oracle JRE | =1.7.0-update60 | |
Oracle JRE | =1.8.0-update5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.