Remote Shell
Bind & Reverse Shell
I have personnally found bind and reverse shell confusing, but with the rigth perspective it is not confusing at all.
There are 2 systems involved in this process - your system from which the "hack" is initiated, lets call it the "hacker"(192.168.1.1) and the other system that falls "victim"(10.11.1.1), lets call it the "victim". Now in order for the hacker to gain remote shell of the victim system, the hacker needs to establish a connection between the two. As we know when a connection has to be established there has to one system waiting to receive the connection and the other initiating the connection.
Bind Shell - When the hacker gets the victim to listen on a port and then initiates a connection from his system to the victim's systems it is a bind shell connection.
Reverse Shell - When the hacker gets his/her system to listen on a port and then initiates a connection from the victim's system, it is a reverse shell conneciton.
Remote Shell using Netcat
Netcat is a popular tool to create remote shells when Linux machines are involved. The bind and reverse shell confusions kicks in when the commands have to redirected to the respective shells of the operating system.
Bind Shell using 2 Linux Systems
Victim
Hacker
Reverse Shell using 2 Linux Systems
Hacker
Victim
In the case of victim's system being Windows the execution has to be "-e cmd.exe"
Remote Shell using Powershell on Windows
Powershell is a very powerfull scripting language that is part of Windows since Windows 8. Powershell commands can be used for creating remote shells and this is a very popular method to gain control of a remote system.
Reverse Shell When Victim runs a Windows System
Hacker
Victim
Bind Shell When Victim runs a Windows System
Victim
Hacker
Last updated