Last Updated on May 24, 2015
Did you update your Java Plug-in with the Update 7 after the critical vulnerability discovered last week? You’d better wait!
Adam Gowdiak, CEO of Security Exploration, the Polish startup that discovered the Java SE 7 vulnerabilities (immediately exploited by cyber criminals), has discovered a new flaw that affects the patched version of Java released this Thursday. A patch released outside the consolidated Oracle update cycle which foresees three updates per year: an uncommon event for the company which demonstrates the seriousness of the security hole.
Unluckily, history is repeating, Adam Gowdiak has told The Register, that just-released Java SE 7 Update 7, contains a flaw that could allow an attacker to bypass the Java security sandbox completely, making it possible to install malware or execute malicious code on affected systems.
Even more unluckily, history is totally repeating: as happened for the previous vulnerability, the bug was reported to Oracle in April 2012 (and unfortunately is not yet patched).
At this point there is no other choice than disabling Java from your favourite browser.
If you want to know if your browser is vulnerable, you can click the following link: http://www.isjavaexploitable.com/.
If you want to know how to disable Java in your environment, you can find detailed instructions at these links by Brian Kerbs or Naked Security.
Disable Java or Die!
Pingback: Java security exploit. « slientpoison
wow, Max. wake up with some sand in your vagina?
Pingback: Antisec Steals 12M Apple Device ID from FBI (Exploiting a Java Vulnerability) « Hackmageddon.com
“Disable Java or Die!” Well FUCK YOU I hope Microsoft and Google are paying you well for this propaganda.
Your kind are nothing but whores. I´m sure if ORCL put you on a contract these kind of posts would be nonexistant or much more lenient.
Thanks for your kind words. For the chronicle no one is paying me for blogging. I only think that a vulnerability, sorry two vulnerabilities, unpatched since April 2012 are quite curious. Don’t you think so?
Pingback: Oops, They Did it Again! New Vulnerability Discovered in Just-Patched Java | Hackmageddon.com « 0518091101's Blog
Pingback: CVE-2012-4681 – Java 7 vulnerabile. Lo è anche la nuova Patch! | Gianni Amato