大网数据广告活动
网络与域名解析

Be Wary of Other RPC Endpoints Running in the Same Process

· 52CE 我爱测

When an application resides in a process with other RPC servers, all applications listen on all protocols.

When an application resides in a process with other RPC servers, all applications listen on all protocols. As such, if a component calls RpcServerUseProtseq* for LRPC only, it is not necessarily accessible over LRPC only. It may be accessible over other protocols, since other RPC servers in the process may be listening on pipes or sockets (for example).

Similar to strict context handles, not putting another endpoint in the process does not mean another endpoint does not exist. Regardless of how you register your server, there is no special association between your interface and your endpoint; all interfaces are callable on all endpoints in that process. This is another reason why the endpoint security model is ineffective; if a security descriptor is placed on an endpoint, attackers can call the interface on another endpoint.

To ensure a process be called only on a specific protocol sequence, register a security callback function, and in that function, check on which protocol sequence the call is made.

Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Win32 documentation
适用范围
Windows Win32 API · Source date 05/31/2018
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。