SharpRDP : RDP Application For Authenticated Command Execution

SharpRDP is a Remote Desktop Protocol Console Application for Authenticated Command Execution.

Building

To compile open the project in Visual Studio and build for release. Two DLLs will be output to the Release directory, you do not need those because the DLLs are in the assembly.

If you do not want to use the provided DLLs you will need to .NET SDK to create the AxMSTSCLib.dll DLL. To create it you’ll need to run aximp from the SDK on mstscax.dll. %<SDK dir>%\aximp.exe %windir%\system32\mstscax.dll.

Those DLLs will need to be referenced by the project to get the Interop DLLs created. You will also need to compress the DLLs with Deflate and name them AxInterop.MSTSCLib.dll.bin and Interop.MSTSCLib.dll.bin

Usage

Regular RDP connection and execution
SharpRDP.exe computername=target.domain command=”C:\Temp\file.exe” username=domain\user password=password

Exec program as child process of cmd or powershell
SharpRDP.exe computername=target.domain command=”C:\Temp\file.exe” username=domain\user password=password exec=cmd

Use restricted admin mode
SharpRDP.exe computername=target.domain command=”C:\Temp\file.exe”

Connect first host drives
SharpRDP.exe computername=domain.target command=”\tsclient\C\Temp\file.exe” username=domain\user password=password connectdrive=true

Execute command elevated through Run Dialog – CURRENTLY BUGGED
SharpRDP.exe computername=domain.target command=”C:\Temp\file.exe” username=domain\user password=password elevated=winr

Execute command elevated through task manager
SharpRDP.exe computername=domain.target command=”C:\Temp\file.exe\” username=domain\user password=password elevated=taskmgr

Add Network Level Authentication
SharpRDP.exe computername=domain.target command=”C:\Temp\file.exe\” username=domain\user password=password nla=true

Ask to take over logon session
SharpRDP.exe computername=domain.target command=”C:\Temp\file.exe\” username=domain\user password=password takeover=true

If restricted admin mode is enabled on the target do not specify any credentials and it will use the current user context. Can PTH or make_token in beacon or runas /netonly on a Windows system.

All execution starts with the Windows run dialog (Win+R). There will be a registry key created at HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\RunMRU with the command that you executed. If you want to remove this you can use: CleanRunMRU: Get or clear RunMRU values

Keep in mind if you execute a program like msbuild (I’m sure there are others) a cmd window will pop up while the process is running. If you do it would probably be best to migrate the process and kill the original.

The required DLLs are compiled into the assembly and app domain assembly resolve event is used. Because of the size of the DLLs they are compressed and decompressed at runtime (so they could meet beacon’s 1MB size limit).

R K

Recent Posts

The Growing Role of Digital Libraries in Remote Education

Learning Without Walls Remote education has long been a lifeline for students in rural areas…

2 days ago

How Do I Do Reverse Image Search

Have you ever come across a picture on the internet and wondered where it came…

3 days ago

WhatsMyName App – Find Anyone Across 640+ Platforms

Overview WhatsMyName is a free, community-driven OSINT tool designed to identify where a username exists…

2 weeks ago

Analyzing Directory Size Linux Tools Explained

Managing disk usage is a crucial task for Linux users and administrators alike. Understanding which…

2 weeks ago

Understanding Disk Usage with du Command

Efficient disk space management is vital in Linux, especially for system administrators who manage servers…

2 weeks ago

How to Check Directory Size in Linux

Knowing how to check directory sizes in Linux is essential for managing disk space and…

2 weeks ago