How hackerhouse-opensource/compmgmtlauncher_dll_uacbypass works
Main Components
• CompMgmtLauncher Component: Represented by the project folder “CompMgmtLauncher_DLL_UACBypass”. This holds the main executable logic that gets auto-elevated on some Windows versions.
• Proxy DLL Component: Represented by the “Secur32” folder (as Secur32.dll). It is the DLL that is “hijacked” in the search order to inject code.
• Operating System & Environment: Include Windows 10/11 as the underlying platforms with specifics regarding auto-elevation and DLL search order behavior.
• OneDrive & Sharepoint: Since the exploit relies on OneDrive’s default installation and reading pattern (as well as persistence via Microsoft.Sharepoint.exe on Windows 11), include them as external components impacting the exploit chain.
Incorporating Architectural Patterns and Design Principles
• Modularity: You have a clear separation where the launcher code and the injected DLL are in different projects, which should be depicted as separate modules.
• Dependency: The exploitation relies heavily on environmental conditions (e.g., OneDrive presence, OS version vulnerabilities), so these dependencies must be clearly annotated.
• Platform-Specific Behavior: Highlight differences between x64 and x86 deployments to signal that architecture-specific branches or logic may affect the injection and exploitation approach.
Relevant Technologies and Frameworks
• Visual Studio / MSVC: Both projects use Visual C++ project files (.vcxproj, .cpp, .rc) which are important to design-time and build process.
• Exploitation Context: Mark necessary details such as the use of auto-elevation (autoelevate-enabled binaries) and the interaction with OneDrive and potential Microsoft.Sharepoint.exe exploitation.