L2J Server

Overview

Java 7 Update 10 and earlier contain an unspecified vulnerability that can allow a remote, unauthenticated attacker to execute arbitrary code on a vulnerable system.

Description

The Oracle Java Runtime Environment (JRE) 1.7 allows users to run Java applications in a browser or as standalone programs. Oracle has made the JRE available for multiple operating systems.

The Java JRE plug-in provides its own Security Manager. Typically, a web applet runs with a security manager provided by the browser or Java Web Start plugin. Oracle's document states, "If there is a security manager already installed, this method first calls the security manager's checkPermission method with a RuntimePermission("setSecurityManager") permission to ensure it's safe to replace the existing security manager. This may result in throwing a SecurityException".

By leveraging unspecified vulnerabilities involving Java Management Extensions (JMX)MBean components, an untrusted Java applet can escalate its privileges by calling the the setSecurityManager() function to allow full privileges, without requiring code signing. Oracle Java 7 update 10 and earlier are affected.

This vulnerability is being attacked in the wild, and is reported to be incorporated into exploit kits. Exploit code for this vulnerability is also publicly available.

Impact

By convincing a user to visit a specially crafted HTML document, a remote attacker may be able to execute arbitrary code on a vulnerable system.

Solution

We are currently unaware of a practical solution to this problem. Please consider the following workarounds:

Disable Java in web browsers

Starting with Java 7 Update 10, it is possible to disable Java content in web browsers through the Java control panel applet. Please see the Java documentation for more details.

Source: http://www.kb.cert.org/vuls/id/625617

Well that's just sad...

This is a known issue and already discussed in this forum.

this issue is recent.

the other issue that was discussed before is already fixed viewtopic.php?f=4&t=26103

issue solved in Java 7 Update 11

https://blogs.oracle.com/java/entry/jav ... _addressed

I wonder if they change anything else in the new releases other than the bug/exploit fixes...

I bet there's changelog somewhere in their website

That's quite a boring changelog: http://www.oracle.com/technetwork/java/ ... 96856.html
(I know they're release notes, not a changelog, but there doesn't seem to be one).
They've basically just set it so it asks to confirm every time the web plugin tries to run.

Java is still vulnerable, fix doesnt do shit.

mmmm no, because now it will always ask to you to confirm before execute anything.

even with signed/secure applets!

for example (tested in java.com website):


so there is no vulnerability now, except that the user be really dumb and select execute an unknown applet anyway.

which will be user fault xD