PG Algernon

I spent two days on this box. On Friday, I looked through it. I knew the answer was the MS. Remoting Services port. I looked for MS. Remoting exploits to no avail. I try again today and lookup "SmarterMail". I see "SmarterMail Build 6985 - Remote Code Execution" and see it's the reason why that 17001 port is open. I use the exploit and it works. Takes less than 10 minutes.

SmarterMail before build 6985 provides a .NET remoting endpoint which is vulnerable to a .NET deserialisation attack.

Lessons Learned

  1. SmarterMail can have a MS. Remoting Port Service open.
  2. First time seeing SmarterMail.
  3. First time seeing MS. Remoting Port.

Comments

Popular posts from this blog

HTB - Jarvis MySQL

Palo Alto for GNS3 CCDC Tutorial

Trace Labs Global Missing Persons CTF V