In this post, I would like to share a quick tutorial (I guess) on how to setup a VulnHub machine in your local network. I’ll assume that you are already familiar with virtualization and some basics of networking. If you’re not, just follow along because I’m noob as well 🔨 !
What is VulnHub?
VulnHub is a website that provides vulnerable virtual machines (VMs) for those who wants to gain a practical experience in penetration testing. It similar with Hack The Box and TryHackMe, but with VulnHub you can practice locally. Because Windows machine requires a license, most VulnHub machines are Linux server.
There are a lot of things you can do with VulnHub machines after you get a root, such as:
- Analyzing the vulnerability, sometimes I patch it if it’s just an insecure code line.
- Learning how the authors configure the machines.
- Building a pentest lab that consists of VulnHub machines to practice network pivoting.
- DFIR, and many more!
Let’s jump in!
Install Virtualization Software
First thing first, you need a virtualization software such as VirtualBox or VMWare. Here is the links for both software:
- VirtualBox - https://www.virtualbox.org/wiki/Downloads
- VMWare - https://www.vmware.com/products/workstation-player.html
I personally use VirtualBox (Windows) because it’s easy to use (and of course, it’s free), but I’ll update this post if I got another license of VMWare.
Download VM Images / OVA
Assuming that you’ve downloaded and installed a VirtualBox, now get your VulnHub machines/VM images at VulnHub’s official site: https://www.vulnhub.com/.
For this example, I’ll be using symfonos: 2.
Importing VM Images
For the image, if it’s on
zip format make sure to decompress it first. In my case symfonos: 2 is on
7z format, so I have to decompress it.
Here’s what I have after decompressing it.
.ovf file should already be associated with VirtualBox, and we can just double click on that file. It’ll take us straight to the import menu.
To do that manually, open up your VirtualBox then click on the File menu -> select “Import Appliance…”, it will pop a new window.
Click on the icon that I marked with a red box to browse your VM image.
Locate your VM image and then click on the Open button.
For now let’s leave all the settings to its default.
Click on the Import button and wait until it completed.
When the import is done, you will see the machine on the VM list section
Setting Up VM Network
Here is the core part, we’ll be putting the VM in an isolated network.
Open the VM’s settings by right click and choose “Settings”.
Go to the Network section, and set the “Attached to” to
Click OK button.
Now open the adapter configuration on the File menu –> select “Host Network Manager…”.
In the image below, the “VirtualBox Host-Only Ethernet Adapter” will be using a network range of
192.168.2.0/24 and has DHCP server enabled which is needed by VulnHub machines to obtain IP address automatically on boot.
192.168.2.2 is the IP address of the virtual adapter on the host side while
192.168.2.1 is the IP address of the built-in DHCP server from VirtualBox.
Below is the configuration for the DHCP server.
I set my
Lower Address Bound to
Upper Address Bound to
192.168.2.254, so that all machines will be assigned with an IP started from
.100-254, and no one gets
Can I configure it to
Yes you can!
If we want to create a
10.10.10.0/24 network, it’s better to create another adapter by clicking the Create menu (you don’t say) then set the adapter’s settings with
|IPv4 Network Mask||
Next, configure the DHCP server to:
|Lower Address Bound||
|Upper Address Bound||
Then, on the VM settings (symfonos: 2), change the adapter name with the new one we created before
Lastly, we should also configure the attacking machine, in my case it’s Kali Linux, to use the same network adapter.
Boot your machines and we’re done!