MITMProxy_PWNage | ️MITMProxy Ettercap PWNd

Inside of whatever virtualization software you use set up a shared NAT network. As an example, with VirtualBox go to VirtualBox->Preferences->Network and add an NAT Network. The network CIDR can be whatever you want, but for our demonstration we will use 10.0.2.0/24. Give it a name (e.g., NATNetw0rk), and check "Enable Network". Create two virtual machines, we used Ubuntu 18.04 for our "Attack" machine and Lubuntu 14.04 for our "Victim" machine. You can use whatever flavor of Linux you want but be mindful about setup differences. From here on out these machines will be denoted "Attack VM" and "Victim VM", respectively. Configure the network settings of each VM in VirtualBox, make sure their network cards are using the NAT network you created, in our case NATNetw0rk. After the VMs are created, statically assign IPs to each machine by configuring the interfaces in a similar (or identical) fashion.
Inside of whatever virtualization software you use set up a shared NAT network. As an example, with VirtualBox go to VirtualBox->Preferences->Network and add an NAT Network. The network CIDR can be whatever you want, but for our demonstration we will use 10.0.2.0/24. Give it a name (e.g., NATNetw0rk), and check "Enable Network".
Create two virtual machines, we used Ubuntu 18.04 for our "Attack" machine and Lubuntu 14.04 for our "Victim" machine. You can use whatever flavor of Linux you want but be mindful about setup differences. From here on out these machines will be denoted "Attack VM" and "Victim VM", respectively.
Configure the network settings of each VM in VirtualBox, make sure their network cards are using the NAT network you created, in our case NATNetw0rk.
After the VMs are created, statically assign IPs to each machine by configuring the interfaces in a similar (or identical) fashion.
Attack VM /etc/network/interfaces
Victim VM /etc/network/interfaces
Restart the networking service of each VM.
Make sure you can ping each other. For example, from the Attack VM ping 10.0.2.5, and from the Victim VM ping 10.0.2.3. You should be getting responses from both machines. Now we can set up Ettercap on the Attack VM.
sudo sysctl -w net.ipv4.ip_forward=1
sudo apt-get install ettercap-graphical
sudo ettercap -G
Under "Sniff" select "Unified Sniffing" and select the interface that was configured for the Attack VM - in our case it is enp0s3. Select "Ok".
Go into "Hosts" and select "Hosts list" Click "Hosts" again and select "Scan for hosts" Add 10.0.2.1 (default gateway) to "Target 1" Add 10.0.2.5 (Victim VM) to "Target 2"
Now click on "Mitm" and then "ARP poisoning..." Check the "Sniff remote connections." box and click "Ok"
To verify we're getting traffic open a terminal and run sudo tcpdump. In the Victim VM open Firefox and go to google.com and come back to the tcpdump terminal screen and watch the traffic flow. Facebook won't populate on the Victim VM because we're not forwarding anything yet; however, we proved we're getting the traffic from the Victim VM so we can do IP forwarding and setup MITMProxy.
Open preferences of Firefox and search for proxy Manually configure the proxy to localhost port 8080 for HTTP and HTTPS and press OK
In the search bar go to "mitm.it" and download the cert. Check both boxes and accept
Run the plugin
cd firefox && ./install.sh
This installs the MITMProxy certificate and an adequate firefox profile with proxying to port 8080.
Run the plugin