Accenture / AARO-Bugs

Vulnerabilities, exploits, and PoCs
34 stars 21 forks source link

Workflow not precise #1

Open 3isenHeiM opened 4 years ago

3isenHeiM commented 4 years ago

Hi, it's not an issue per say, more of a request for more information.

So far, I've :

However, I don't see the setup.dll in system32.

Any clues ? Am I doing it right ?

In TriDiag, do I need to change CLSID_CollectorService to the correct GUID ?

Many thanks :)

hatRiot commented 4 years ago

Hey @3isenHeiM

A few things:

If you have confirmed all of these things, I would be interested in knowing if there was an RPC error (see here). You can check this by adding a debug function that writes the error code to a file somewhere on your host.

3isenHeiM commented 4 years ago

Hi, thanks for the quick answer ! :)

hatRiot commented 4 years ago

3335_1000_rpc_s.c and 3335_1000_rpc_s.h are not minor versions included in this repository, so the IDL must have compiled. Make sure you add both the .h and .c files to your Visual Studio project before compiling. My suspicion is the IDL/GUID isn't quite right here. Try deleting the .h/.c files, ensure the uuid(...) line in your IDL is correct, then add it to your project, right click, and compile. Then re-add the .h/.c files.

You can check using the Sysinternal's tool procmon. Just run it before you launch DevViewer and filter on the process name and event type.

3isenHeiM commented 4 years ago

Thanks for the explanation :)

Re-compiled the RpcDll.dll, but restrictions on the machine prevent me to run ProcMon. Since the GUI of DevViewer opens, I think the DLL is not loaded. And I don't see setup.dll in the system32 folder.

Besides that : in TrigDiag, where is mentioned the folder in which the FILE_NAME has to be executed ? Does it look by default in the SYSNATIVE folder for it ?

hatRiot commented 4 years ago

Using TrigDiag is only necessary once you've got setup.dll in your System32 folder, so we're not quite there yet.

You can confirm the DLL is being loaded by simply adding a system("calc.exe") or equivalent to your TextInputFramework.dll and checking if calc pops. If it does, please see my earlier comment about adding some debug output. Add a small function to write output to a text file somewhere (or attach to a console) and ensure you print the RPC error, if there is one. My guess is the problem is somewhere there, but I'd have to see the RPC error code to know for sure.