> For the complete documentation index, see [llms.txt](https://ahmed-tarek.gitbook.io/security-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ahmed-tarek.gitbook.io/security-notes/notes/attack-vectors-by-port/msrpc.md).
# MSRPC
**`Default Port: 135, 593`**
**MSRPC (Microsoft Remote Procedure Call)** is the modified version of DCE/RPC. It forms the basis of network-level service interoperability. MSRPC is the protocol standard for Windows processes that allows a program running on one host to execute a program on another host.
### Connect
MSRPC services normally listen on ports `135 and 593`; however, they can also run on other ports.
#### Netcat
You can check the connection with the `netcat` tool:
```
nc -vn 135
nc -vn 593
```
### Enumeration
#### Using Nmap
```
nmap -p 135,593 --script=msrpc-enum
```
#### RPC Client
Windows has an embedded tool for interacting with MSRPC called RPC client that you can use for enumeration.
```
rpcclient -U "" -N
#empty username (-U "")
#no password (-N)
```
```
> serverinfo
> lsaenumsid
> netshareenumall
```
#### Identifying Exposed RPC Services
Exposure of RPC services can be determined by querying the RPC locator service and individual endpoints using tools such as rpcdump. This tool identifies unique RPC services, denoted by IFID values, providing service details and communication bindings.
```
rpcdump [-p port]
```
Tools such as Metasploit can also be used to audit and interact with MSRPC services, primarily focusing on port 135.
```
use auxiliary/scanner/dcerpc/endpoint_mapper
use auxiliary/scanner/dcerpc/hidden
use auxiliary/scanner/dcerpc/management
use auxiliary/scanner/dcerpc/tcp_dcerpc_auditor
```
Among these options, all except tcp\_dcerpc\_auditor are specifically designed for targeting MSRPC on port 135.
### Attack Vectors
MSRPC has several interfaces that could be potentially exploited for gaining unauthorized access, remote command execution, enumerating users and domains, accessing public SAM database elements, remotely starting and stopping services, accessing and modifying the system registry, and more. These interfaces include:
* LSA interface (`pipe\lsarpc`)
* LSA Directory Services (DS) interface (`pipe\lsarpc`)
* LSA SAMR interface (`pipe\samr`)
* Server services and Service control manager interface (`pipe\svcctl`), (`pipe\srvsvc`)
* Remote registry service (`pipe\winreg`)
* Task scheduler (`pipe\atsvc`)
* DCOM interface (`pipe\epmapper`)
You can also use the IOXIDResolver interface to identify IPv4 and IPv6 addresses of systems on the network.
#### MSRPC DCOM
MSRPC DCOM is one of the most dangerous services on Windows systems due to the amount of control it can give an attacker. It should be disabled if not needed. MSRPC endpoints can be abused to execute arbitary code on a remote computer.
```
nmap -p 135 --script=msrpc-dcom-interface-activation
```
---
# 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://ahmed-tarek.gitbook.io/security-notes/notes/attack-vectors-by-port/msrpc.md?ask=&goal=
```
`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.