A new VM… After almost 2 years.

Saying it’s been awhile is an understatement. Almost 2 years without a new vulnerable VM and over 2 years without a blog post. I only have myself to blame, but work and family life takes up most of my waking hours. This is a hobby and hobbies come last.

I must start by saying how shocked I am with the reception my VMs have received since their inception. Over the past 24+ months, I’ve gotten so many nice messages and e-mails from people saying they enjoyed them. A few of my VMs have actually been mentioned in books, which was a pleasant surprise… So to all that have enjoyed them, and used them as reference material (or what have you) a big thank you from the bottom of my heart.

I never expected this little project would turn out the way it did. This just proves, if you put a bit of effort and time, anything can happen.

Why the new VM

Kioptrix VM 2014

The original idea behind my VMs has always been about learning, not only for the people downloading them but for me as well. With each new VM, I always try to do something “different”, something to take me out of my comfort zone… just a bit, just enough so I can learn something new and hopefully remember it. Installing old unsupported software from source on a newer OS or just using a flavour (or flavor) of Linux I’ve never tried before. It doesn’t have to be something huge, just something I don’t know or not too comfortable with. For me, trying and reading is one of the ways I learn.

This new machine is no different. I had an idea in my head, wanted to know a bit more about it and saw an opportunity to apply it in a VM (however g0tm1lk g0tmi1k kind of pushed me a bit to release a new one). I didn’t spend 2 years building this thing, but in the short amount of time it took me to build it (2 weeks… 3?) I got very familiar with what’s in there.

Why build these things…

Which brings me to another point I wish to blabber about, why build these things. As mentioned above, it’s primarily to learn. To experiment and discover different operating systems and software. Get more acquainted with compiling, installing and uninstalling (just to name a few). The great thing about this is, you’ll ask yourself questions and if you’re lucky bugs to look up and fix. At the end of the day, that’s the point really… to figure things out on your own.

If you’re building a VM to submit to vulnhub.com (as an example), then you need to pay attention to how your machine reacts to scans and attacks. You need to figure out what works and what doesn’t.
Why does attack “A” work but not “B”?
What if…
Why this…
Why that… You can learn lots if you take the time to ask yourself questions.

So I’ve come to the part where I’m babbling and writing for the sake of writing which is my queue to stop. Hope you enjoy the new VM.


About the VM

As usual, this vulnerable machine is targeted at the beginner. It’s not meant for the seasoned pentester or security geek that’s been at this sort of stuff for 10 years. Everyone needs a place to start and all I want to do is help in that regard.

Also, before powering on the VM I suggest you remove the network card and re-add it. For some oddball reason it doesn’t get its IP (well I do kinda know why but don’t want to give any details away). So just add the VM to your virtualization software, remove and then add a network card. Set it to bridge mode and you should be good to go.

This was created using ESX 5.0 and tested on Fusion, but shouldn’t be much of a problem on other platforms.
–Update 07-04-2014: Virtual Box users may encounter issues.. sorry

Kioptrix VM 2014 download 825Megs
MD5 (kiop2014.tar.bz2) = 1f802308f7f9f52a7a0d973fbda22c0a
SHA1 (kiop2014.tar.bz2) = 116eb311b91b28731855575a9157043666230432
Waist line 32″
p.s.: Don’t forget to read my disclaimer…


iOS 7 jailbreak

Hi everyone :)

It’s been a long while since my last post I know :). Here’s an interesting article I found about a jailbreak for iOS 7. Not sure if I’m gonna try it … humm … probably yes :P.


Comments ?



I broke on through to the other side … of the blog

Hi everyone,

I know you’re normally used to see @loneferret publish on this side of the website but I thought I could add a post or two once in a while and hopefully translate each french one I do too.

So here’s my first entry :)



Win Free Copies of new book on Advanced Penetration Testing:

Readers would be pleased to know that I have teamed up with Packt Publishing to organize a Giveaway of the Advanced Penetration Testing for Highly-Secured Environments: The Ultimate Security Guide book.

And three lucky winners stand a chance to win copies of their new book. Keep reading to find out how you can be one of the Lucky Winners.



SSL & stunnel

When connecting to port 995 (e-mail SSL accepted server) using a raw TCP connection, nothing will happen since it’s expecting SSL “commands”. So we could type anything we want after the connection is made, and nothing will happen. What we need to do is, encapsulate our “traffic” in SSL. This can be done using stunnel. Visit the author’s site, and have a look around.
If it’s not installed on your Linux distribution then I recommend doing so. There’s also a Windows version as well which I also suggest getting if you want to test out creating a netcat session between 2 machines using an stunnel.

Let’s see how we can go about creating a simple chat session between 2 machines with netcat and stunnel. First let’s setup our listening machine to accept SSL connections on a specified port. Lets start by configuring our client machine to accept traffic on a given port, take that traffic and encapsulate it SSL and sent to socket accepting SSL connections.
First open up stunnel’s config file (I’m my Linux machine as client) and add/modify the following:

client = yes

[netcat client]
accept = 5555
connect = -Listening IP-:4444

Any traffic entering port 5555 will be encapsulated and sent to port 4444 on the target IP as SSL traffic.
Now let’s setup the stunnel service on our listening machine, in this case the Windows system.

client = no
[netcat server]
accept = 4444
connect = 7777


So now that we have stunnel setup on both machines, let’s start the connection using netcat.
From our listening system, or serve:

C:\>nc -vlp 7777

And now, let’s connect from our Linux system:

Linux~# nc -nv 5555

If everything went according to plan, the Linux box connects to local port 5555 which is then encapsulated and sent to the listening’s IP address which is expecting an SSL conneciton. One should be able now to “chat” between the two systems. One can also receive a reverse-shell this way, or connect to a pop3 mail server which only accepts SSL connections on the default port 995.


Update 16-12-2011:
This was written some time ago, and things may have changed. Although everything is still relevant you may need to change or adjust your sTunnel settings on you Linux and Windows machine.

Update 16-07-2012:
Due to a change in ownership, the new hosting company uses content filtering for “security reasons”. This means many of my previous posts can no longer be displayed. So I’m re-posting them avoiding the “bad” words..