Ncat client --ssl with -e does not work on Windows

[dmiller-nmap]

Reported:

I was conducting a red team test the other day and noticed that when I was trying to send a cmd.exe using the --ssl option of ncat to a remote ncat listener on a Linux box, although the connection did return and we could see the shell popping, whenever you try typing any command, it becomes unresponsive and the ncat on the Windows box seems to be entering a big loop of printing out debugging messages becoming unresponsive as well.

When I used ncat through socat so that socat did the ssl encryption, it worked fine.

[schnippe]

please see duplicate #1274

[schnippe]

please see duplicate #1274

[dmiller-nmap]

In my testing, change 420618c fixes the SSL error, but I don't get any further output from the shell. Entering dir doesn't return any output. On the client side (ncat --ssl -e cmd localhost) I see

NCAT DEBUG: i == WAIT_OBJECT_0

every time I strike Enter on the server (shell) side.

[dmiller-nmap]

In my testing, change 420618c fixes the SSL error, but I don't get any further output from the shell. Entering dir doesn't return any output. On the client side (ncat --ssl -e cmd localhost) I see

NCAT DEBUG: i == WAIT_OBJECT_0

every time I strike Enter on the server (shell) side.

[dmiller-nmap]

All right! Fix is in SVN, will be mirrored to Github within an hour. Problems included:

1. WaitForMultipleObjects only tells you the first of the events that signalled,
2. SSL_read doesn't clear the event, so WaitForMultipleObjects keeps notifying that the socket needs a read.

So the subprocess never got a chance to send any data to the socket.

[dmiller-nmap]

All right! Fix is in SVN, will be mirrored to Github within an hour. Problems included:

1. WaitForMultipleObjects only tells you the first of the events that signalled,
2. SSL_read doesn't clear the event, so WaitForMultipleObjects keeps notifying that the socket needs a read.

So the subprocess never got a chance to send any data to the socket.

[gvanem]

How did this get closed? The fix doesn't even compile. See my comment here.

[gvanem]

How did this get closed? The fix doesn't even compile. See my comment here.