More FUD. The actual threat level of this 'bug' is the same as the linux/windows root access ones that require local access to a server. And all this noise shows a profound level of ignorance on how classes are actually loaded by the jvm.
The JVM does not deserialize classes that it cannot access -- so this means that you cannot send it a random class for deserialization -- you'll just get a classnotfound exception if you try that. You can only deserialize a class the jvm knows about.
So in order to trigger this bug, you will need to know what classes the jvm has in its classpath, know what versions of those classes exist (the VM will refuse to deserialize a class that is a different version from that in the classpath), and know if the vm will accept a stream of bytes for deserialization.
Remember most java servers (weblogic/jboss/tomcat) are all running behind apache.
That's not to say that this is not a bug -- but it is a bug in a specific library and does not really call for this level of panic.
Foxglove demonstrated the attack against WebSphere via a SOAP request to the AdminService and a similar attack against JBoss via a request to the JMXInvoker service. Any javax.management port that uses remote object serialization and has vulnerable libraries is potentially vulnerable. Any server running RMI is potentially vulnerable, but if RMI ports are open to the Internet, the server has bigger security problems to worry about.
If your admin ports are open to the internet, you have other things to worry about.
I'm not sure what kind of mickey mouse operation you're working with but that's a terrible approach. Shit might as well leave the front door open then...
You know that's not what I said. You're not designing a house, you're designing a castle. You need to plan for what happens when the thieves bring ladders and scale your walls.
Just trying to keep them out is not enough. You need to actively design your security to keep them from doing damage once they're inside.
23
u/curiousthis Nov 23 '15
More FUD. The actual threat level of this 'bug' is the same as the linux/windows root access ones that require local access to a server. And all this noise shows a profound level of ignorance on how classes are actually loaded by the jvm.
The JVM does not deserialize classes that it cannot access -- so this means that you cannot send it a random class for deserialization -- you'll just get a classnotfound exception if you try that. You can only deserialize a class the jvm knows about.
So in order to trigger this bug, you will need to know what classes the jvm has in its classpath, know what versions of those classes exist (the VM will refuse to deserialize a class that is a different version from that in the classpath), and know if the vm will accept a stream of bytes for deserialization.
Remember most java servers (weblogic/jboss/tomcat) are all running behind apache.
That's not to say that this is not a bug -- but it is a bug in a specific library and does not really call for this level of panic.