# hackerhouse-opensource/iscsicpl_bypassuac architecture

> Architecture diagram of the GitHub repository hackerhouse-opensource/iscsicpl_bypassuac, 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/iscsicpl_bypassuac
- Repository: https://github.com/hackerhouse-opensource/iscsicpl_bypassuac

## Overview

1. iscsicpl_BypassUAC – This component is likely responsible for triggering or setting up the exploit against iscsicpl.exe. Its files (a .cpp source, a resource file, and accompanying project files) indicate that it builds the final executable that leverages the vulnerability.
2. iscsiexe – This project builds the malicious payload (a proxy DLL) that is expected to be discovered and loaded by the iscsicpl.exe binary, thanks to the vulnerable DLL search order. This component resembles a DLL but is structured as a standalone project directory; note the pch files and resource files that support this module.

The README clarifies the exploit’s mechanism: when a 32-bit version of iscsicpl.exe (running under SysWOW64 on 64-bit Windows) searches for iscsiexe.dll, the malicious version provided by this project in the user’s %Path% is loaded, allowing code execution with elevated privileges.

- Vulnerable Component: iscsicpl.exe – Represent this as the trusted Microsoft binary running in the Windows environment (specifically under SysWOW64). Although it is not part of this repository, it is the target.
- Exploit Launcher: iscsicpl_BypassUAC – This is your custom executable that sets up or triggers the vulnerability.
- Malicious DLL/Proxy Payload: iscsiexe – This is the proxy DLL that gets loaded through the DLL search order hijacking, executing the payload code.

b. Relationships and interactions:
- That iscsicpl.exe, upon being executed, performs a DLL search in the user’s %Path% and locates the malicious iscsiexe.

c. Important architectural and design principles:
- Crossing of privilege boundaries—how a user-land vulnerability (DLL search order hijacking) is used to bypass UAC.
- Separation of exploit setup (iscsicpl_BypassUAC) and payload delivery (iscsiexe) which corresponds to modular design.
- Mention the reliance on Windows dynamic linking behavior as a core dependency.

d. Relevant technologies and frameworks:
- Microsoft Visual Studio tools (VC++ project structure, .sln files, .vcxproj).
- The Windows operating system’s DLL search mechanism and security features (like UAC).
- The concept of auto-elevation available for certain binaries (iscsicpl.exe in this case).

- For this exploit tool, rather than a full-stack client-server model, focus on the interplay between a trusted system binary and a malicious DLL.
- Security-relevant aspects: vulnerabilities, privilege escalation, and the runtime behavior resulting from the DLL search hijack.
- Use annotations to explain how the environment (user %Path%, SysWOW64) influences the DLL load order.

- Clear, descriptive labels for each component: “iscsicpl.exe (Trusted Windows Binary)”, “iscsicpl_BypassUAC (Exploit Launcher)”, and “iscsiexe (Malicious Proxy DLL)”.

## Diagram (Mermaid)

```mermaid
flowchart TD
    A["Windows Environment (SysWOW64)"]:::os
    B["iscsicpl_BypassUAC (Exploit Launcher)"]:::exploit
    C["iscsicpl.exe (Trusted Windows Binary)"]:::vuln
    D["iscsiexe (Malicious Proxy DLL)"]:::payload

    A -->|"executes"| C
    B -->|"triggers"| C
    C -->|"DLL load (via search order hijacking)"| D

    click B "https://github.com/hackerhouse-opensource/iscsicpl_bypassuac/blob/main/iscsicpl_BypassUAC/iscsicpl_BypassUAC.cpp"
    click D "https://github.com/hackerhouse-opensource/iscsicpl_bypassuac/blob/main/iscsiexe/iscsiexe.cpp"

    classDef os fill:#d1e8e2,stroke:#333,stroke-width:2px
    classDef exploit fill:#ffd966,stroke:#333,stroke-width:2px
    classDef vuln fill:#f4cccc,stroke:#333,stroke-width:2px
    classDef payload fill:#c9daf8,stroke:#333,stroke-width:2px
```
