How hackerhouse-opensource/mssettingsdelegateexecute works
Project Type and Purpose
• This is a Visual Studio C++ project designed to compile a static x64 binary that demonstrates a bypass of User Account Control (UAC) on Windows 10/11 using a vulnerability in the ms-settings DelegateExecute registry key.
• The target use case is security testing and proof-of-concept validation for this specific UAC bypass vulnerability.
Analyzing the File Structure
• The root includes the Visual Studio solution file (MsSettingsDelegateExecute.sln) alongside the README.md.
• The main project folder (MsSettingsDelegateExecute) contains:
• The primary source file (MsSettingsDelegateExecute.cpp), which is expected to contain the logic for triggering the vulnerability.
• A resource file (.rc) and corresponding header (resource.h) indicating the inclusion of additional static resources needed during compilation or execution.
• The Visual C++ project file (.vcxproj) and its filters file (.vcxproj.filters) that define how the project is built and organized.
• Source Code & Resources:
• Build System:
• Windows Execution Environment:
• Compiled binary running in the Windows environment (Windows 10/11 x64).
• UAC Bypass Mechanism:
• Ms-settings DelegateExecute mechanism as the core vulnerability exploitation vector. Show its connection to the Windows registry and UAC subsystem.
• Security Interaction:
• Interaction between the binary and the Windows security model (i.e., how the binary uses the registry key misconfiguration to bypass UAC).
Relationships and Interactions
• Compiled binary to the Windows Operating System block.
• Optionally, include a feedback loop from the OS’s security aspects (UAC controls) back to the binary to illustrate that the binary leverages the flawed ms-settings behavior.
Architectural Patterns and Principles
• The project is fairly straightforward—a single C++ project designed to demonstrate a specific exploit. The key design principle is minimalism, with all functionality embedded in one compiled binary.