Objective 5 wants us to use the already made VM imageand find the user’s login name.
(You can download the file here, if you wish to use it)
If we have completed CURLing Master Cranberry Pi terminal challenge by Holly Evergreen, then we can get a hint which is.
“Unencrypted HTTP/2? What was he thinking? Oh well.
Have you ever used Bloodhound for testing Active Directory implementations?
It’s a merry little tool that can sniff AD and find paths to reaching privileged status on specific machines.
AD implementations can get so complicated that administrators may not even know what paths they’ve set up that attackers might exploit.
Have you seen anyone demo the tool before?”
Also, a hint link.
Well, let’s get started. First thing first we need to import the VM image into our favourite VM software, VirtualBox, VMware Workstation Pro, VMware Workstation Player and many others out there!
I’m going to be using VMware Workstation Pro to import this VM image, use file – open and find the downloaded (.ova) file, or double click on it (depending on how you set up your VM software)
(Note: Some users have reported issues with it not starting, and have said changing the setting to 64-bit fixed it).
Once you have the (.ova) imported start it up and wait for it to load.
As we can see, there isn’t much here, on the desktop we have the following Trash, File system, Home and a link to starting Bloodhound.
I did look around the file system, and there isn’t anything here, but if you want a copy of the wallpaper here you go!
The hint by Holly Evergreen and the URL link all links together about Bloodhound, so that’s what we use.
BloodHound loads itself, and you see this screen once done.
“BloodHound uses graph theory to reveal the hidden and often unintended relationships within an Active Directory environment.” Bloodhound is a significant tool! So I won’t be covering it in this guide. However, Raphael Mudge has a great starter video on it here.
Let’s get this challenge compleated! Click on the three lines, then head over to queries, find the “shortest paths to domain admins from kerberoastble users” and then select the domain admin group “Domain [email protected]
Once you have done all of this, you then be on this screen, as long as everything has gone correctly!
Remember the challenge details? “Remember to avoid RDP as a control path as it depends on separate local privileges escalation flaws” So, RDP just forget about it in this challenge, and the task itself is for us to “find a reliable path from a kerberoastble user to the domain admin group”.
We need to find a reliable path from a kerberoastble user to the domain admin group; this is where we need to get too.
Looking at the BloodHound again and if we remove the RDP paths, we can see were only left with one way to the admin groups.
So that path is called “[email protected]” it’s the shortest route to admin groups and doesn’t have any RDP on the way either.
[email protected] is our answer!