Not so fast: Java 7 Update 7 critical vulnerability discovered in less than 24 hours
Polish security firm Security Explorations has sent an advisory, with a proof-of-concept exploit, to Oracle today (Friday 31 AUG) specific to a vulnerability they discovered in the Java 7 security update released Thursday. This newly reported vulnerability can be exploited to escape the Java sandbox and execute arbitrary code on the underlying system.
Standby for more on this one, no word yet from Oracle regarding their remediation plans.
As Rapid7's Tod Beardsley has said: "As it happens, very few websites rely on Java for dynamic content. Java isn't relied on nearly as much as Javascript and Flash. Most people can disable their Java browser plugin and not really notice the difference."
What mitigations are you utilizing to protect yourselves? Going so far as disabling Java all together? Feedback welcome via comments.
See Scott's post from yesterday for the original advisory details.
Comments
So the real danger here is when companies using these services is been hacked, and the hacker get hold on important information.
Regards Robert
ww.webbfabriken.com
robert
Aug 31st 2012
1 decade ago
JJ
Sep 1st 2012
1 decade ago
ts
Sep 1st 2012
1 decade ago
All sensible persons was against requiring client Java (The applets needs to have full control over your machine, such that the government can use it to install spyware ^H^H^H^H^H^H check your machine for malware (which they do not do)). But it is difficult to talk sense into government or their semi-public implementation partners.
Other government sites, like import/export registration not only requires Java, but often breaks if you have installed a version not at least 10 patches old.
All this just shows how government organizations is completely out of touch with the real world.
Rumors are, that the citizen ID will move to a non-Java implementation within a couple of years, but they are always late with their implementations. The problem is, that all the sites depending on citizen ID will not work in most browsers (mobile devices).
The danish government puts its citizens at risk.
PHP
Sep 3rd 2012
1 decade ago
http://www.infoworld.com/d/security/6-ways-protect-against-the-new-actively-exploited-java-vulnerability-201174
I reviewed and because we have to have it for a few internal applications, but may only need for a VERY limited few external applications, I believe that method 2 (Java only working in TRUSTED sites) may be a fairly safe configuration. You would then have to manage Trusted sites for business users, but seems like it would be fairly easy to manage AND allow granularity based on Group membership (policy driven Registry Management).
EVVJSK
Sep 4th 2012
1 decade ago
Joe
Sep 4th 2012
1 decade ago