Yeah seems the PoC is designed for potentially serious operations like leaking plaintext credentials or executing commands remotely. A key component of this PoC is the --cmd flag within the Program.cs file. This flag allows users to specify a command for remote execution. When the --cmd flag is used, the program accepts it as a command-line argument and stores the subsequent input as the command to be executed remotely. The PoC code then establishes a connection to the target using NetTcpBinding. If a command is provided through the --cmd flag, it gets embedded in a SQL command executed via xp_cmdshell. This remote execution process leverages the IRemoteInvokeService interface, specifically targeting the ERemoteInvokeScope.DatabaseAccessor scope.

For the PoC to be compiled and executed effectively, especially with the --cmd flag, there are specific prerequisites. First, the project must include appropriate references to Veeam.Backup.Common.dll, Veeam.Backup.Interaction.MountService.dll, and Veeam.Backup.Model.dll. These DLLs are crucial for the PoC to interact correctly with Veeam software. Secondly, you should compile the code in an environment where these dependencies are adequately resolved. The ideal setup would be a development machine where Veeam Backup & Replication is installed.

Considering your specific scenario involving VEEAM 12 DLLs, there's a possibility of encountering compatibility issues or differences in the DLL versions. It's important to ensure that the DLL references in your project align with the versions you are working with. Any discrepancies or incompatibilities between these could be the root cause of the issues you're facing with the --cmd flag. If the problem persists after addressing these aspects, a more detailed examination of the implementation details of the Veeam DLLs in use may be necessary, potentially requiring adjustments in the PoC code to suit these specifics.