JRMPClient payload: how does it work? about ysoserial HOT 4 CLOSED

The author of this is @mbechler and there's some minimal docs in the source code, but my understanding is that exploit.JRMPClient is for directly exploiting DGC listeners (i.e. if there isn't a DGC listener open, it won't work).

https://github.com/frohoff/ysoserial/blob/master/src/main/java/ysoserial/exploit/JRMPClient.java#L21

/**
 * Generic JRMP client
 * 
 * Pretty much the same thing as {@link RMIRegistryExploit} but 
 * - targeting the remote DGC (Distributed Garbage Collection, always there if there is a listener)
 * - not deserializing anything (so you don't get yourself exploited ;))
 * 
 * @author mbechler
 *
 */

It's hard to say what the issue is without seeing the exception, but in the future you're probably better off asking usage/support type questions in the gitter chat https://gitter.im/frohoff/ysoserial.

from ysoserial.

Should probably have named the client and the payload differently to avoid confusion ;)

Usage for payloads.JRMPClient:

• Launch a exploit.JRMPListener somewhere where the remote host can connect to with the secondary payload you like (generally the payload is only useful if the secondary payload is present on your exploitation target but you cannot get it there because there is some filter on the ObjectInputStream)
• Deliver the payloads.JRMPClient with the address/port that the listener is reachable on
• Now the remote end should try to contact that listener for performing distributed garbage collection, that call delivers the secondary payload via an exception. That connection should be visible in the output of JRMPListener.
• Remote deserializes exception (iirc with the TCCL from handling the original call) with a stock ObjectInputStream -> there you go.

What kind of exception are you seeing? A ClassCastException would be expected (and in that case I guess you should see the request coming in, if the address is correct and reachable). Unfortunately the code that the reverse call is made in swallows any exceptions so if you need to go further you would have to attach a debugger (code in question should be DGCClient$Endpoint.makeCleanCalls) to see what is wrong.

from ysoserial.

Thanks! I will follow-up in the gitter chat.

from ysoserial.

Thanks. Closing.

from ysoserial.