# hackerhouse-opensource/compmgmtlauncher_dll_uacbypass architecture

> Architecture diagram of the GitHub repository hackerhouse-opensource/compmgmtlauncher_dll_uacbypass, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-03-16). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/hackerhouse-opensource/compmgmtlauncher_dll_uacbypass
- Repository: https://github.com/hackerhouse-opensource/compmgmtlauncher_dll_uacbypass

## Overview

##### 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.

## Diagram (Mermaid)

```mermaid
flowchart TD
    %% External Environment
    A["Windows Environment (Windows 10/11, auto-elevation & DLL search order)"]:::env

    %% Launcher Module
    B["CompMgmtLauncher_DLL_UACBypass (Launcher Executable)"]:::launcher

    %% DLL Search Process
    C["DLL Search Process<br/>(if OneDrive installed)"]:::process

    %% OneDrive Injection Point
    D["OneDrive Folder (DLL Injection Point)"]:::external

    %% Proxy DLL Module
    E["Secur32 (Proxy DLL)"]:::proxy

    %% Persistence/Execution Module
    F["Microsoft.Sharepoint.exe (Persistence/Execution)"]:::external

    %% Interactions
    A -->|"auto-elevates"| B
    B -->|"initiates DLL search"| C
    C -->|"searches in"| D
    D -->|"loads hijacked DLL"| E
    E -->|"injects code for UAC bypass/persistence"| F

    %% Click Events for components
    click B "https://github.com/hackerhouse-opensource/compmgmtlauncher_dll_uacbypass/tree/main/CompMgmtLauncher_DLL_UACBypass"
    click E "https://github.com/hackerhouse-opensource/compmgmtlauncher_dll_uacbypass/tree/main/Secur32"

    %% Styles
    classDef env fill:#FFD700,stroke:#000,stroke-width:2px;
    classDef launcher fill:#87CEEB,stroke:#000,stroke-width:2px;
    classDef process fill:#D3D3D3,stroke:#000,stroke-width:2px;
    classDef external fill:#FFB6C1,stroke:#000,stroke-width:2px;
    classDef proxy fill:#90EE90,stroke:#000,stroke-width:2px;
```
