This mentions the name of this release, when it was released, who made it, a link to 'series' and a link to the homepage of the release.
It's common for an author to release multiple 'scenarios', making up a 'series' of machines to attack.
Here you can download the mentioned files using various methods.
We have listed the original source, from the author's page. However, after time these links 'break', for example: either the files are moved, they have reached their maximum bandwidth limit, or, their hosting/domain has expired.
For these reasons, we have been in touch with each author asking for permission to mirror the files. If the author has agreed, we have created mirrors. These are untouched copies of the listed files. (You can check for yourself via the MD5 & SHA1 checksums which are individually displayed on their entry page. See how here).
We also offer the download via BitTorrent. We prefer that people use BitTorrent, however, we do understand that it is not as straight forward as clicking on a direct link.
To make sure everyone using VulnHub has the best experience possible using the site, we have had to
limit the amount of simultaneous direct download files to two files, with a max speed of 3mb
This is because the average file size is currently about 700mb, which causes our bandwidth to be high (couple of terabytes each month!). As this is a privately funded project, we believe we have chosen the best hosting provider for the limited budget.
If would you like to be able to download a mass, and at quicker speed, please use torrents as these will be seeded 24/7. For a guide on how to setup and use torrents, see here.
If you're the owner of a listed file or believe that we are unlawfully distributing files without permission, please get in touch here.
This section is for various information that has been collected about the release, such as quotes from the webpage and/or the readme file.
These sources of information are usually helpful towards the completion of the release as the author can drop hints* as well as methods to help get the release up and working.
* This is a 'little' hint. Useful to help you get started and it shouldn't give anything away that you quickly could find out for yourself.
To make sure that the files haven't been altered in any manner, you can check the checksum of the file.
This makes sure that the you have acquired the same file which was transferred to you, without being modified/changed/damaged.
Some authors publish the checksums in the README files, on their homepages or sometimes inside compressed archive (if it has been compressed).
VulnHub also lists the MD5 & SHA1 checksums for every file which it offers to download, allowing you to check. You can find all the checksums here, otherwise, they will be individually displayed on their entry page. To check the checksum, you can do it here.
You can find out how to check the file's checksum here.
The links below are community submitted 'solutions' showing hints/nudges or possibly a complete walkthrough* of how they solved the puzzle.
Please note, there could be (many) more methods of completing this, they just haven't, either been discovered, or submitted. If you know something that isn't listed, please submit it or get in touch and we would be glad to add it.
* This is a spoiler. It could possibly show you a way of completely solving it.
What is mentioned here are possible flags/challenges to find/try after 'completing' the machine by gaining the highest level possible*.
The author might put something in, after you gain complete control over the machine. 'Flags' are placed to prove that you gained access. Challenges create something 'extra' to do.
Please note, there could be (many) more flags/challenges in these machines, they just haven't been discovered or submitted. If you know something which existing in this machine that isn't listed, please submit it or get in touch.
* This is a hint. It hopefully prompts the attacker to keep on looking after gaining access over the machine, as 'shell is only the beginning' -- Carlos Perez.
The list here, is of all the known & published vulnerabilities*.
This was added to allow the attacker to perform a certain exploit/technique. For example, practises doing Cross Site Scripting (XSS).
Please note, there could be (many) more vulnerabilities in these machines, they just haven't been discovered or submitted. If you know of something that exists in this machine but isn't listed, please submit it or get in touch.
* This is a spoiler. By looking at this list, it will 'let the cat out of the bag', by disclosing possible methods of completing this release.