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.
3
u/jbristow Nov 23 '15
What do you think of these exploits? https://github.com/frohoff/ysoserial
They're pretty scary, and the one on a standard Jenkins install makes me nervous for all the random build servers that get set up in datacenters...
https://tersesystems.com/2015/11/08/closing-the-open-door-of-java-object-serialization/
From this article, it looks like if you have ObjectInputStream in your classpath, then you're vulnerable, even if your ports are non-obvious.