search
GitHubPsMapExec

Fusion Corp

https://tryhackme.com/room/fusioncorp

hashtag
Nmap

sudo nmap 10.10.75.130 -sS -sV -p-

PORT      STATE SERVICE       VERSION
80/tcp    open  http          Microsoft IIS httpd 10.0
88/tcp    open  kerberos-sec  Microsoft Windows Kerberos (server time: 2021-06-20 13:33:25Z)
135/tcp   open  msrpc         Microsoft Windows RPC
139/tcp   open  netbios-ssn   Microsoft Windows netbios-ssn
389/tcp   open  ldap          Microsoft Windows Active Directory LDAP (Domain: fusion.corp0., Site: Default-First-Site-Name)
445/tcp   open  microsoft-ds?
464/tcp   open  kpasswd5?
593/tcp   open  ncacn_http    Microsoft Windows RPC over HTTP 1.0
636/tcp   open  tcpwrapped
3268/tcp  open  ldap          Microsoft Windows Active Directory LDAP (Domain: fusion.corp0., Site: Default-First-Site-Name)
3269/tcp  open  tcpwrapped
3389/tcp  open  ms-wbt-server Microsoft Terminal Services
5985/tcp  open  http          Microsoft HTTPAPI httpd 2.0 (SSDP/UPnP)
9389/tcp  open  mc-nmf        .NET Message Framing
49666/tcp open  msrpc         Microsoft Windows RPC
49667/tcp open  msrpc         Microsoft Windows RPC
49672/tcp open  ncacn_http    Microsoft Windows RPC over HTTP 1.0
49673/tcp open  msrpc         Microsoft Windows RPC
49678/tcp open  msrpc         Microsoft Windows RPC
49690/tcp open  msrpc         Microsoft Windows RPC
49697/tcp open  msrpc         Microsoft Windows RPC
Service Info: Host: FUSION-DC; OS: Windows; CPE: cpe:/o:microsoft:windows

Starting off I attempted basic SMB enumeration and was unable to enumerate any meaningful information. From here I moved to LDAP and used the Nmap script shown below to pull domain information.

From this we ascertain the domain name is 'Fusion.Corp'. From this we can start enumerating Kerbeos.

Kerberos

Install Kerbrute: https://github.com/ropnop/kerbrutearrow-up-right

Storing the discovered users in a file called 'asrep-hashes'. I then run GetNPUsers from Impacket against both the discovered usernames in order to retrieve Kerberos hashes.

Viewing the contents of asrep-hashes we see we have a hash for the user lparker.

Running this against Hashcat shows we soon crack the password.

We are then able to utilize the credentials against port 5985 with Evil-WinRM.

After grabbing the user flag on the Desktop I started working through basic enumeration. First checking local user accounts we see some interesting information for the user jmurphy.

We are then able to login with Evil-WinRM using the new credentials.

Again, the user flag can be grabbed from the Desktop. From here and as per the above image we see we have the privilege 'SeBackupPrivilege'.

This privilege grants us the ability to create backups of files on the system. Knowing this a high value file would be the ntds.dit file which is a database of hashes for domain objects / users. As the ntds.dit file is in constant use we will be unable to create a backup using normal methods as the system will lock the file.

What we can do instead is create a Distributed Shell File (DSH). This file will contain the appropriate commands for us to run the diskshadow utility against the C: drive and ultimately the ntds.dit file.

First created a file called viper.dsh on the attacking machine. Then insert the following contents:

Once completed use the command unix2dos to convert the file to DOS format.

Then on the target system create a directory called 'temp' in c:\temp. After this upload the viper.dsh file.

From here run the following commands:

From here we need to extract the SYSTEM hive which will be required for extracting the hashes with Impacket later.

From here we can use the download command to download the ntds.dit and system hive file.

Back on the attacking machine use the following command with Impacket to extract the hashes from ntds.dit.

From here we have the Administrator hash which can be used to login to the target system with Evil-WinRM.

We are now Administrator on the Domain Controller and can grab the final flag from the Desktop.

Last updated