About Release

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.

Breach-3.0.1.zip

Download

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.

Third in a multi-part series, Breach 3.0 is a slightly longer boot2root/CTF challenge which attempts to showcase a few real-world scenarios/vulnerabilities, with plenty of twists and trolls along the way.

Difficulty: Intermediate, requires some creative thinking and persistence more so than advanced exploitation.

The VM is configured to grab a lease via DHCP.

A few things:

1) This is the culmination of the series, keep your notes close from the previous 2 challenges, they may come in handy.
2) Remember that recon is an iterative process. Make sure you leave no stone unturned.
3) The VM uses KVM and QEMU for virtualization. It is not necessary to root every host to progress.
4) There are 3 flags throughout, once you reach a flag you have achieved that intended level of access and can move on. These 3 flags are your objectives and it will be clear once you have found each and when it is time to move on.

Shout-out to knightmare for many rounds of testing and assistance with the final configuration as well as g0blin, Rand0mByteZ, mr_h4sh and vdbaan for testing and providing valuable feedback. As always, thanks to g0tmi1k for hosting and maintaining Vulnhub.

If you run into any issues you can find me on Twitter: https://twitter.com/mrb3n813 or on IRC in #vulnhub.

Looking forward to the write-ups!

Enjoy and happy hunting!

SHA1: EBB2123E65106F161479F3067C68CFA143CA98D3

For the time being, there will not be HTTP download links - only a torrent.
v3.0 - 23/02/2017
v3.0.1 - 10/03/2017

Description

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.

Checksum

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.

Walkthroughs

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.