This machine present in the private lab was made public in Vulnhub so I’m giving it another run. The virtual machine is up but I have no idea which IP address is assigned to it, so where’s our target? ┌─[root@rocinante]─[/home/w1zard/Documents/lab/vulnhub/lampiao] └──╼ #arp-scan -I eth1 192.168.58.0/24 Interface: eth1, datalink type: EN10MB (Ethernet) Starting arp-scan 1.9.5 with …
Here goes a quick tip, but mostly a reminder to myself. After a fresh install of your favorite pentest distro, upon making a search on the Metasploit for the first time you’ll get the warning message below: [!] Module database cache not built yet, using slow search What to do? The answer is quite simple. …
Another machine available during the CEH course, but this one was pretty straight forward. The description fo this machine is telling us the OS is not up-to-date anymore and the vendor support is over, so lets look for active services: root@parrot:~# nmap -sV -O 192.168.10.103 Nmap scan report for 192.168.10.103 Host is up (0.015s latency). …
This was one of the first machines done during the CEH course. The virtual machine available in my classes was a copy of another existent in the lab so, when I finally got access to the lab, I merely replicated the actions done in the VM and this let the description of the machine in …
So, there’s this penetration test laboratory which I received access when I attended the CEH course. You have access to a task list with the targets, each target has its own page providing the machine’s IP address, a tip not very helpful in most cases and the flag location. It’s similar to a few other …