> For the complete documentation index, see [llms.txt](https://capcap-1.gitbook.io/capcap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://capcap-1.gitbook.io/capcap/readme/ctf-modules/information-gathering/service-enumeration/windows-remote-management-protocols/wmi-135.md).

# WMI (135)

Use this page to enumerate WMI and understand its RPC and DCOM execution flow.

### WMI (Windows Management Instrumentation)

WMI is Microsoft’s design scaling of the Common Information Model (CIM) metadata framework.

It functions as an un-isolated system information warehouse, retaining real-time read and write access across nearly every underlying component configuration in the environment.

### Network protocol handshake matrix

WMI relies on DCOM (Distributed Component Object Model) connection mechanisms, presenting a split-port network execution curve:

1. **The core anchor (TCP port `135`)** — all terminal communication initializations target port `135` to reach the RPC Endpoint Mapper.
2. **Dynamic high-port transitions** — once authentication passes, the server runtime assigns a temporary dynamic port configuration and immediately moves the entire remaining interaction stream to that ephemeral channel.

### Remote lateral movement

Because WMI can query, start, or alter native operating system background objects such as services or processes, it is heavily used by security professionals to perform stealthy lateral movement.

#### Command execution via Impacket suite

```bash
# Launch specific targeted commands remotely using valid credentials from Linux
/usr/share/doc/python3-impacket/examples/wmiexec.py <username>:"<password>"@<TARGET_IP> "hostname"
```

### Summary protocol breakdown reference

| **Protocol framework name** | **Standard network ports**                      | **Communication vector type**            | **Primary shell execution interface**      | **Target tool tracking signatures**       |
| --------------------------- | ----------------------------------------------- | ---------------------------------------- | ------------------------------------------ | ----------------------------------------- |
| RDP                         | `3389` (TCP / UDP)                              | Graphic User Interface screen matrix     | Full interactive GUI desktop               | `xfreerdp`, `mstshash=nmap` cookie marker |
| WinRM                       | `5985` (HTTP) / `5986` (HTTPS)                  | XML text blocks over SOAP wrappers       | PowerShell command line interface          | `evil-winrm`, `Test-WsMan`                |
| WMI                         | `135` (RPC initialization) + Dynamic High Ports | DCOM structural operating system objects | Semi-interactive system terminal execution | `wmiexec.py`                              |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://capcap-1.gitbook.io/capcap/readme/ctf-modules/information-gathering/service-enumeration/windows-remote-management-protocols/wmi-135.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.