NetCat & PowerShell -> disaster

Of course I’m being a little to dramatical, after so many days of admiring the new windows shell, and even after writing an article about it on darknet the problems started to fall in. Actually I know just this single issue but I told you I’m too dramatical. One little note before debating the problem: I do not make guilty for this issue nobody, except those MS programmers… kidding… you guys just continue developing powershell and people like me will be looking for bugs instead of you :)

Bugs – here they come

How it all begin? I was playing with netcat, when I got the great idea to use powershell as it’s win shell, instead of the old command prompt. Everything was ok until I connected to my listening net cats… by the way I used it as a bindshell, and as a reverse shell like:

—
nc -l -e powershell.exe -t -p 666 //bindshell
telnet localhost 666 //to connect

nc -l -p 666 //reverse shell
nc -e powershell.exe localhost 666 //to connect
—

Didn’t you understand?

What really is happening is that throe PowerShell bindshell has become reverse shell and reverse shell bindshell. Confusing? I don’t think so, just take a look at how the response is being carried, I mean the less useful result goes where it should go, and the waited result goes where it shouldn’t go…. but what am I talking here if you ever used netcat, you’ll know what I an talking about…