Skip to content
Universal Dynamic Virtual Channel connector for Remote Desktop Services
C++ C
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
UDVC-Plugin close socket, terminate thread when channel closing Mar 18, 2018
UDVC-Server
wiki
.gitattributes
.gitignore initial commit for UDVC Server Mar 9, 2018
README.md
UDVC-Plugin.reg
UDVC-Plugin.sln UDVC Plugin initial commit Mar 11, 2018

README.md

Universal Dynamic Virtual Channel connector for Remote Desktop Services (UDVC)

Terminal Services (or Remote Desktop Services) are offering many hidden features for those who want to dig deeper. One of these services is the Dynamic Virtual Channel that enables us to communicate over an open RDP connection without the need to open a new socket, connection or a port on a firewall. These channels can be used to hide data from active network devices, to bypass firewalls, to implement device drivers over networks or just to help penetration testers to transfer data. The possibilities are endless.

The real reason why this project was created is XFLTReaT. This could be used to build up a "VPN" over segregated networks and finally it enables testing over jumpboxes without requesting firewall changes. In a nutshell it makes penetration testers' life easier.

How does this work?

You need to install a plugin (.dll) on your client computer that you use to connect to the RDP server. On the RDP server you need to use the other half of the project the .exe, which creates the channel between the plugin and the server executable. If you want to know more details, please scroll down.

Installation

It is Windows only. Dynamic Virtual Channels were introduced in Window Server 2008 & Windows Vista SP1. These and anything newer than these should be good to go.

You can grab the whole project and compile it by yourself or just use the compiled binaries from the Releases section. It is important that the correct binary is used in all cases, please select the correct one for the corresponding architecture (if your client is 32bit but the server is 64bit then grab the 32bit dll and 64bit exe). The .dll needs to be placed on the client computer in any directory (for long-term use, you can put it into the %SYSROOT%\system32\ or %SYSROOT%\SysWoW64\) and install it with the following command as an elevated user (a.k.a Administrator): regsvr32.exe UDVC-Plugin.dll

If your user is not an administrator, you need to import the registry settings under your user too. Please use the UDVC-Plugin.reg file for that.

If you wish to remove it: regsvr32.exe /u UDVC-Plugin.dll

Every time you connect to an RDP server from now on, this plugin will be loaded and will configure itself as it was specified in the registry (see below).

The .exe needs to be put on the RDP server and run as any user.

Modes supported

Both sides support three modes at the moment:

Socket server mode (0 - default)

When this mode is enabled, then a listener will be set up on the defined port and interface (IP address).

Socket client mode (1)

In this mode a connection will be made towards a listener on the defined IP address and port.

Named Pipe mode (2)

This mode sets up a Named Pipe with the specified name. As an example: this mode can be used for other tools to do IPC communication over RDP. Unfortunately, Named Pipes are written to the disk so it is considered slow compared to the socket modes. If you care about the bandwith, please use the socket modes.

Options/Configuration

Both the client and the server binary act the same way and it can be configured with the same options.

  • enabled: 0 disabled, 1 enabled (plugin only). By default it is enabled and will tell you in a messagebox every time you initiate a connection.
  • mode: 0 for listen(), 1 for connect() and 2 for creating a Named Pipe
  • ip: which UP to connect to or bind to
  • port: which port to connect to or bind to
  • namedpipename: name of the named pipe
  • priority (server binary only) LOW, MEDIUM, HIGH, REAL priorities for data transmission. REAL priority could severely affect the accessibility of the session in case of an intense data transfer, since the protocol prioritizes data over the control.

The server binary will read the options from the command line.

PS C:\Users\UDVC\> .\UDVC-Server.exe -h
Universal Dynamic Virtual Channel server application

Usage: C:\Users\UDVC\UDVC-Server.exe [-s | -c [-p port [-h ip]] | -m [-n name]] [-0 | -1 | -2 | -3]
Socket server mode -s (default) OR
Socket client mode -c:
        -p port   port to bind the listener (default: 31337)
        -i ip     ip to bind the listener (default: 127.0.0.1)

Named pipe mode -m:
        -n name   name of the named pipe (by default: "\\.\pipe\UDVC_{RDP SESSION NUMBER}")

Data transfer priority parameters:
        -0        real time             (WTS_CHANNEL_OPTION_DYNAMIC_PRI_REAL)
        -1        high priority         (WTS_CHANNEL_OPTION_DYNAMIC_PRI_HIGH) - default
        -2        medium priority       (WTS_CHANNEL_OPTION_DYNAMIC_PRI_MED)
        -3        low priority          (WTS_CHANNEL_OPTION_DYNAMIC_PRI_LOW)

The client .dll reads all the options from the registry, the values can be found under the following key: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Terminal Server Client\Default\AddIns\UDVC-Plugin

Every time the module is enabled and before the connection is made a reminder warning is showed. Just like this: warning This warning ensures that the user knows about the plugin is loaded and with what settings.

Usage

The listeners, connections or named pipes are only created when the server executable was able to connect to the plugin dll. It depends on your configuration, but by default when the Virtual Channel connection was made (the plugin was loaded properly, the server binary was executed) it listens on the localhost:31337 on both endpoints. When you connect to these ports and send data through the socket, it will show up on the other side.

Example use cases

Just to show a few uses cases where this tool can be used.

Very basic port forwarding. The Segregated 1 machine has a HTTP service on tcp/80. That network is not routed from the 192.168.0.0/24 network, the dual homed jump box must be used to access. Listen mode is configured on the client side on 0.0.0.0:31337 and the server binary was executed with the connect mode settings to create a connection to the web server. The user on the RDP client can use its browser to open http://127.0.0.1:31337 to access the content from http://10.13.37.2:80. scenario1

A bit more advanced scenario to transfer files. Both endpoints are configured to listen on 0.0.0.0:31337. First the Hacking box connects to the RDP client and waits for the input. Then the Segregated 2 machine connects to the Jump box and reads the whole file into the socket. scenario2

As an extra, Named Pipes can be used as well. In this case both the RDP client and Jump box create a Named Pipe on both sides (hIPC-client and hIPC-server) and the other machines can connect to these pipes. Whatever is written on the pipes it will show up on the other end. It is not really different from the listen mode example above, except it is using Named Pipes instead of TCP sockets. scenario3

Issues

In case the plugin does not load or the executable does not run because it is missing some DLLs for example the VCRUNTIME140.DLL, you might want to install the Visual C++ Redistributable for Visual Studio 2015 package.

You can’t perform that action at this time.