[wildfly-dev] Concerns about deserialization attacks
emond.papegaaij at topicus.nl
Tue Nov 10 03:29:17 EST 2015
As you probably know, there has recently been quite some discussion about
remotely exploitable attacks via deserialization, for instance  and .
These exploits are demonstrated against commons-collections 3 and 4, spring 4
and groovy 2.4.4, but it is very likely other libraries (if not the jdk
itself) also contain vulnerable code. In general, the advise is to not accept
any serialized objects on a public interface.
WildFly multiplexes its remote EJB invocation over the http port via http-
remoting. I've found a way to make a WilfFly instance, configured with the
default standalone.xml, accept arbitrary serialized objects. Access to port
8080 is all you need. I've been able to verify the commons-collections exploit
by adding commons-collections to the right module and let WildFly deserialize
my objects. So far, I've not been able to exploit WildFly using only the
classes available via this route, but I've got the feeling that this is only a
matter of time.
As this is potentially sensitive information, I'm looking for a less public
channel to share the details.
More information about the wildfly-dev